city-app

Plugin city-app from marketplace city-app-framework in balbonits/city-app-framework. Commands read from the repo's manifest — yesterday.

Skills (3)

• lesson

  Make a correction stick across sessions. Use when the human corrects a behavior they'd want fixed for good ("don't do X", "we always do Y", "you did Z again"), or asks you to remember a rule for this project.

• setup

  Set up this project for AI coding agents. Installs AGENTS.md (with CLAUDE.md importing it) and the safety hooks, then fills AGENTS.md from what the repo shows. Safe to re-run; never overwrites existing files. Use --check to only report what's missing.

• start

  Start a new app or feature from a short spec, tests first. Saves the spec to docs/spec.md, turns each requirement into a failing acceptance test, then builds until they all pass. Use when the human describes something new to build in a few sentences ("build me...", "start a...").

Slash commands (5)

• /city-app:rules:prune

  Re-test the AGENTS.md rules saved by /city-app:rules:test, for example after a model update, and cut the ones the agent no longer needs. Shows the plan first and runs nothing until you say yes.

• /city-app:rules:test

  A/B-test one AGENTS.md rule on this project. Runs the same small task with and without the rule in throwaway copies and scores each run with a check command, so you know whether the rule changes what the agent does. Shows the plan first and runs nothing until you say yes.

• /city-app:ui:baseline

  Approve how the pages look now as the baseline. After that, /city-app:ui:check (and npm test, when it runs the UI checks) fails when a page looks different, naming the page and screen size, with a diff image. Use after a visual change the human wanted.

• /city-app:ui:check

  Check the pages you changed for accessibility problems, console errors, and layouts wider than the screen, at phone, tablet and desktop sizes. Pass/fail checks with fix-it messages, plus screenshots. Use after UI changes. --add-test makes npm test run them, so the finish gate enforces them.

• /city-app:ui:tokens

  Check that every color comes from a design token (var(--name)) instead of being written out in CSS, inline styles or element.style. Fails with file:line fix-it messages. --add-test puts it in npm test, so the finish gate enforces it.

Similar plugins