ui-spec-sim
Skill2 starsChanged 4 months agoNo licenceView on GitHub
チケットや要件から「HTML UIスペック (決定ログ D番号・未決Qカード・文言一覧)」と 「触って遷移を確認できるHTMLシミュレーター (カバレッジ自動チェック付き)」のペアを artifactとして作り、ユーザーレビューを何巡も回して確定させる設計レビューループ。 各巡で敵対的な整合検証 (スペック⇔シミュレーター⇔文言表) を行い、確定した内容だけを 実装Ticket/Confluenceに最低限のテキストで同期する。Figma納品はfigma-shot-boardに委譲。 Use when the user wants an interactive UI spec, a transition simulator, a decision-log driven design review, or to iterate a UI design with confirmable state transitions. Triggers: "ui-spec-sim", "/ui-spec-sim", "UIスペックとシミュレーター", "スペックシミュレーター", "設計レビューループ", "遷移を触って確認できるものを作って", "トランジションシミュレーター", "デザイン決定ログでレビュー", "interactive spec", "transition simulator", "spec with simulator".
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-panelSkill
- agents-initSkill
- agent-swarmSkill
- chrome-useSkill
- codex-cliSkill
- codex-serverSkill
- confluenceSkill
- deepenSkill
- dev-workflowSkill
- diagnoseSkill
- dotnet-seniorSkill
- e2e-testSkill
- en-to-ja-explainerSkill
- figma-shot-boardSkill
- gdrive-cliSkill
- grill-meSkill
- grill-to-implSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- japanese-tech-writingSkill
- jira-cliSkill
- local-skill-factorySkill
- logo-imageSkill
- my-gdriveSkill
- my-skill-factorySkill
- naturalize-jaSkill
- natural-japaneseSkill
- notion-cliSkill
- openai-cliSkill
- orch-qaSkill
- parallel-investigateSkill
- playwright-cliSkill
- pm-reviewSkill
- postmortemSkill
- prd-councilSkill
- prototypeSkill
- pr-reviewSkill
- recap-to-notionSkill
- review-localSkill
- scenario-genSkill
- self-pr-reviewSkill
- session-handoverSkill
- session-recapSkill
- session-watchSkill
- skill-improveSkill
- slack-cliSkill
- slack-to-ticketSkill
- subagent-genSkill
- tddSkill
- test-scenarioSkill
- to-prdSkill
- triageSkill
- well-arch-costSkill
- well-arch-reliabilitySkill
- well-arch-securitySkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.