screen-to-spec
Skill0 starsChanged 2 months agoMITView on GitHub
Draft or update a screen spec markdown from an existing UI component. Requires docs/development/stack-paths.md to be filled in.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/docker-compose-local.mdcCursor rule
- .cursor/rules/github-cli-pr.mdcCursor rule
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If any required field is empty → STOP.
- Distinctive: line 19
Read component, styles, routes, and related API calls.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Screen to spec
Component or screen name: $ARGUMENTS
Gate: stack-paths.md
- Read
docs/development/stack-paths.md - If any required field is empty → STOP. Tell user to fill stack-paths and retry.
Steps
- Locate component under
implementation_root(Grep/Glob by name). - Read component, styles, routes, and related API calls.
- Draft
docs/product/screens/<kebab>.mdusing_template.mdstructure. - Note gaps as open questions in the spec.
Output
- Path to created/updated spec file
- Suggested follow-up for
/spec-to-screenif code should be refactored to match spec
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
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.