domain
01Bandersnatch0x/design-playbook
Agent Claude Code
Missing files → proceed silently; create via grill/domain-modeling when needed.
Design I/O plugin for Claude Code & coding agents — declarations + contracts that make UI generation constrained, reviewable, and recirculatable. Not a style pack; composes with ui-ux-pro-max + frontend-design.
Bandersnatch0x/design-playbook
Agent Claude Code
Missing files → proceed silently; create via grill/domain-modeling when needed.
Bandersnatch0x/design-playbook
Agent Claude Code
GitHub Issues carry bug tickets only — defects in shipped behavior that anyone could report. Every other planning artifact (specs, research notes, non-bug work tickets, wayfinder maps) lives as local files under .agents/ (gitignored, never pushed). Use the gh CLI for all GitHub operations.
Bandersnatch0x/design-playbook
Agent Claude Code
A workflow for preparing the packages/design-playbook collection to become a publicly installable Design I/O plugin.
Bandersnatch0x/design-playbook
Agent Claude Code
Manual gate. Automated checks (JSON, layout, frontmatter, clean surface, bundled MCP layout, fixed npm release-group consistency, README badges, release notes present, seam test, adapter floor self-check) run via python scripts/release.py (dry-run) or python scripts/release.py --apply (creates the tag). Static…
Bandersnatch0x/design-playbook
Agent Claude Code
Operational protocol for the fixed human comprehension check on the read-only Run Console. This document prepares a trial; it does not run one.
Bandersnatch0x/design-playbook
Agent Claude Code
The engineering skills use five canonical triage roles. This file maps those roles to the GitHub labels used by this repository.
Bandersnatch0x/design-playbook
Agent Claude Code
Operational list for one interactive greenfield Design I/O run that proves package surfaces before release prep.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: