ng-prototype
Skill13 starsChanged 43 days agoMITView on GitHub
Build a throwaway Angular prototype to flesh out a design before committing – either a runnable terminal app for state/business-logic questions, or several radically different UI variations on one route, switchable from a floating bar. Use when the user wants to prototype an Angular feature, mock up a screen, sanity-check a data model or state machine, explore design options, or says "prototype this", "try a few designs", or "let me play with it".
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .junie/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- angular-developerSkill
- brainstormingSkill
- code-reviewSkill
- create-a-skillSkill
- create-e2e-testsSkill
- diagnosing-bugsSkill
- frontend-designSkill
- git-stack-rewriteSkill
- grill-meSkill
- grill-with-styleSkill
- handoverSkill
- implement-planSkill
- ng-accessibilitySkill
- ng-data-accessSkill
- ng-formsSkill
- ng-migrateSkill
- ng-performanceSkill
- ng-refactorSkill
- ng-review-architectureSkill
- ng-review-style-guideSkill
- ng-securitySkill
- ng-signal-storeSkill
- ng-stylingSkill
- ng-testingSkill
- ng-verify-featureSkill
- spartanSkill
- test-driven-developmentSkill
- unslopSkill
- update-skills-directorySkill
- update-skillsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Before editing, read only the relevant local style guide files – these and AGENTS.md override any generic example here or in the branch …
- Very specific: line 37
Skip the polish: No tests, no .spec.ts, no error handling beyond what makes the prototype _runnable_, no abstractions.
- Distinctive: line 38
Surface the state: After every action (logic) or on every variant switch (UI), render the full relevant state so the user can see what …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Angular prototype
A prototype is throwaway code that answers a question. The question decides the shape. This is the Angular path: prototypes live in this workspace's single Angular CLI app (ng serve / ng build, code under src/app) and follow its real patterns.
Read first
Before editing, read only the relevant local style guide files – these and AGENTS.md override any generic example here or in the branch files:
- TypeScript:
style-guide/style-guide.ts.md - Templates:
style-guide/style-guide.html.md - SCSS:
style-guide/style-guide.scss.md - Accessibility (required for UI – AXE + WCAG AA):
style-guide/style-guide.a11y.md
Pick a branch
Identify which question is being answered – from the user's prompt, the surrounding code, or by asking if the user is around:
- "Does this logic / state model feel right?" → references/logic.md. A tiny interactive terminal app that drives the state machine through cases that are hard to reason about on paper.
- "What should this look like?" → references/ui.md. Several radically different UI variations on one Angular route, switchable via a
?variant=query param and a floating bottom bar.
The two branches produce very different artifacts – getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default by the surrounding code (a service or data model → logic; a page or component → UI) and state the assumption at the top of the prototype.
Rules for both branches
- Throwaway from day one, and clearly marked as such. Locate the prototype next to where it will actually be used so context is obvious, but name it so a casual reader sees it's a prototype, not production. Obey the app's existing routing convention; don't invent a new top-level structure.
- One command to run. Use the workspace runner – the dev server on
http://localhost:4200for a UI prototype (reuse it when it answers; never startpnpm start/ng servewithout explicit approval, perAGENTS.md); apnpm <name>script for a terminal logic prototype. The user must be able to start it without thinking. - No persistence by default. State lives in memory. Persistence is the thing the prototype is checking, not something it depends on. If the question is explicitly about persistence, hit a scratch store with a clear "PROTOTYPE – wipe me" name.
- Skip the polish. No tests, no
.spec.ts, no error handling beyond what makes the prototype runnable, no abstractions. Learn something fast, then delete it. - Surface the state. After every action (logic) or on every variant switch (UI), render the full relevant state so the user can see what changed.
- Delete or absorb when done. Fold the validated decision into the real code or delete it – don't leave it rotting in the repo.
When done
The answer is the only thing worth keeping from a prototype. Capture it somewhere durable – a commit message, an ADR, an issue, or a NOTES.md next to the prototype – along with the question it was answering. If the user is around, that capture is a quick conversation; if not, leave the placeholder so the verdict can be filled in before the prototype is deleted. Each branch's final step then handles its own cleanup.
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.

