agentleFS
santiquisssantiquiss/HeroCanvas/.claude/skills/new-proposal/SKILL.md

new-proposal

Skill5 starsChanged 13 days agoApache-2.0View on GitHub

Design a change to the connected app as a HeroCanvas proposal (proposals/<slug>) - new or replaced pages and components, versions to compare, and the handoff spec for whoever builds it - without touching the mirror of the app as it is. Use when the person wants to explore, propose, redesign or add a feature, or asks for "a version" of a screen.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. chakmarebel/federal-proposal-copilot★ 4same name
    2. christopheryeo/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never copy the mirror: import from app/ what doesn't change (relative imports), and from the tool only herocanvas.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

A proposal

The mirror (app/) is the app as it is. A change to it is a proposal: its own folder that declares only what it adds or changes, picked in the toolbar, shared by link (?proposal=PJ-3), compared side by side with the app as it is (Compare), and handed off with a specification.

proposals/<yyyy-mm-slug>/
  proposal.json   code, title, status, author, created, summary, description, ticket
  pages.tsx       export default proposal({ pages, components, variants })   (optional)
  components/     new or replaced components, with their stories              (optional)
  handoff.md      what changes, in the app's terms, for whoever builds it

1. Ask where it goes

A change to what's on screen is a proposal unless the app changed (or the mirror got it wrong): then it's a fix to the mirror (mirror-screen). Ask if it isn't clear.

2. Create it

  • The code: npm run proposal:code prints the next one (PJ-1: P, the author's initials, their number). It never changes and is never reused.
  • proposal.json: the code, a title, status: 'draft', the author, today's date, a one-sentence summary.
  • Pages: a new page, or a base page replaced by id (spread it to change only some fields: { ...BASE_PAGES.today, component: TodayV2 }). Components: replace one the screens render with overridable (from herocanvas), or add new ones in components/. Versions (variants: A, B…) to compare designs of the same change.
  • Where it shows (show): a changed component that isn't on its page as it loads (it shows for a new user, after a tap, in a state) declares where to see it: show: { Card: { page: 'dashboard', state: { persona: 'emily' }, label: 'as Emily, who signed up today' } } (a version may have its own). The changes popover opens it there, outlined, and Pages marks that page changed. The same by a page's id when a page it changes shows its change only in a state (a closing screen after a tap): show: { checkIn: { page: 'checkIn', state: { ck: 'updated' }, label: 'Get reminded' } }. A replacement marks its root with the component's name (useComponent or <Component name>), so Inspect and the outline find it.
  • Never copy the mirror: import from app/ what doesn't change (relative imports), and from the tool only herocanvas.

3. The handoff

handoff.md: what changes in each component and screen, in the app's terms (its components, their parameters, its tokens, its routes), the logic, the data it needs, the texts in every language, and what stays as it is. A part for one version under ### Version A. Keep it current with every change: the Proposal panel builds the file for whoever implements it from this.

4. Show it

npm run shot -- "/<route>?proposal=<code>" --compare: the app as it is beside the proposal. Phones and tablets, light and dark. Show the person, iterate, and move the status on when they say so: draft, review (someone has to look at it), handed-off (shown as Dev handoff: its ticket for the developers, ticket). Dropped: "archived": true. Built in the app: merged into Live and its folder deleted.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.