Name: reframe
Author: yhyu13

Prompt file imported from yhyu13/AgentHarness101 (.codex/prompts/reframe.md). Fill in {{arguments}} before use. Copyright stays with the author.

description: OpenWolf's design brain — pick/migrate UI frameworks or audit/fix UI against the anti-generic design principles argument-hint: [migrate [framework] | audit [target] | fix [target]]

Arguments: {{arguments}}

Read .wolf/reframe-frameworks.md first — it contains the Design Principles (anti-generic mandate), the framework knowledge base, and the migration prompts. Use .wolf/anatomy.md to locate UI files instead of scanning.

Pick the mode from the arguments (default: migrate if a framework is named or the user is choosing one; otherwise ask which mode they want):

Mode: migrate [framework]

Framework selection and migration.

If no framework is named, ask the Decision Questions from the knowledge file (stop early once the answer narrows to 1–2 options) and recommend one.
Use that framework's prompt from the knowledge file, adapted to this project's real structure via .wolf/anatomy.md.
The Design Principles override anything generic in the prompt: no template hero→features→CTA structures, no stock palettes — distinctive by default.

Mode: audit [target]

Walk the target (default: the whole UI) and flag every match against the AI-tell blocklist in the Design Principles: purple gradient heroes, glassmorphism-everything, emoji headings, generic 3-column feature grids, stock Tailwind palette, Inter for every role, template SaaS structure, filler microcopy. Produce a findings table — component, tell matched, severity, specific replacement direction — and end with the 3 changes that would most increase distinctiveness.

Mode: fix [target]

Run the audit, then fix findings in severity order. Fixes must move toward, not merely away: typography chosen with intent, a palette derived from the product's actual brand/domain, asymmetry where it serves hierarchy, copy specific to what the product does, density appropriate to the audience. Preserve the existing framework and component APIs — this is a design pass, not a rewrite. After each fix, state what changed and why it reads as designed-on-purpose.

Acceptance criterion for every mode: if the result could be swapped onto any other product without anyone noticing, it fails.

Install reframe and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

--- description: OpenWolf's design brain — pick/migrate UI frameworks or audit/fix UI against the anti-generic design principles argument-hint: [migrate [framework] | audit [target] | fix [target]] --- Arguments: {{arguments}} Read `.wolf/reframe-frameworks.md` first — it contains the **Design Principles (anti-generic mandate)**, the framework knowledge base, and the migration prompts. Use `.wolf/anatomy.md` to locate UI files instead of scanning. Pick the mode from the arguments (default: `migrate` if a framework is named or the user is choosing one; otherwise ask which mode they want): ## Mode: migrate [framework] Framework selection and migration. 1. If no framework is named, ask the Decision Questions from the knowledge file (stop early once the answer narrows to 1–2 options) and recommend one. 2. Use that framework's prompt from the knowledge file, adapted to this project's real structure via `.wolf/anatomy.md`. 3. The Design Principles override anything generic in the prompt: no template hero→features→CTA structures, no stock palettes — distinctive by default. ## Mode: audit [target] Walk the target (default: the whole UI) and flag every match against the AI-tell blocklist in the Design Principles: purple gradient heroes, glassmorphism-everything, emoji headings, generic 3-column feature grids, stock Tailwind palette, Inter for every role, template SaaS structure, filler microcopy. Produce a findings table — component, tell matched, severity, specific replacement direction — and end with the 3 changes that would most increase distinctiveness. ## Mode: fix [target] Run the audit, then fix findings in severity order. Fixes must move toward, not merely away: typography chosen with intent, a palette derived from the product's actual brand/domain, asymmetry where it serves hierarchy, copy specific to what the product does, density appropriate to the audience. Preserve the existing framework and component APIs — this is a design pass, not a rewrite. After each fix, state what changed and why it reads as designed-on-purpose. Acceptance criterion for every mode: **if the result could be swapped onto any other product without anyone noticing, it fails.**

{ "prompt": "---\ndescription: OpenWolf's design brain — pick/migrate UI frameworks or audit/fix UI against the anti-generic design principles\nargument-hint: [migrate [framework] | audit [target] | fix [target]]\n---\n\nArguments: {{arguments}}\n\nRead `.wolf/reframe-frameworks.md` first — it contains the **Design Principles\n(anti-generic mandate)**, the framework knowledge base, and the migration prompts.\nUse `.wolf/anatomy.md` to locate UI files instead of scanning.\n\nPick the mode from the arguments (default: `migrate` if a framework is named or the\nuser is choosing one; otherwise ask which mode they want):\n\n## Mode: migrate [framework]\nFramework selection and migration.\n1. If no framework is named, ask the Decision Questions from the knowledge file\n (stop early once the answer narrows to 1–2 options) and recommend one.\n2. Use that framework's prompt from the knowledge file, adapted to this project's\n real structure via `.wolf/anatomy.md`.\n3. The Design Principles override anything generic in the prompt: no template\n hero→features→CTA structures, no stock palettes — distinctive by default.\n\n## Mode: audit [target]\nWalk the target (default: the whole UI) and flag every match against the AI-tell\nblocklist in the Design Principles: purple gradient heroes, glassmorphism-everything,\nemoji headings, generic 3-column feature grids, stock Tailwind palette, Inter for\nevery role, template SaaS structure, filler microcopy. Produce a findings table —\ncomponent, tell matched, severity, specific replacement direction — and end with the\n3 changes that would most increase distinctiveness.\n\n## Mode: fix [target]\nRun the audit, then fix findings in severity order. Fixes must move toward, not merely\naway: typography chosen with intent, a palette derived from the product's actual\nbrand/domain, asymmetry where it serves hierarchy, copy specific to what the product\ndoes, density appropriate to the audience. Preserve the existing framework and\ncomponent APIs — this is a design pass, not a rewrite. After each fix, state what\nchanged and why it reads as designed-on-purpose.\n\nAcceptance criterion for every mode: **if the result could be swapped onto any other\nproduct without anyone noticing, it fails.**", "variables": [ "arguments" ], "notes": "Arguments: ${arguments}", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/yhyu13/AgentHarness101", "path": ".codex/prompts/reframe.md", "ref": "fc7d9ea7925c603405b17db2500f2f7d6ccbe291", "url": "https://github.com/yhyu13/AgentHarness101/blob/fc7d9ea7925c603405b17db2500f2f7d6ccbe291/.codex/prompts/reframe.md", "key": "yhyu13/AgentHarness101/.codex/prompts/reframe.md" } } }

reframe

About

description: OpenWolf's design brain — pick/migrate UI frameworks or audit/fix UI against the anti-generic design principles argument-hint: [migrate [framework] | audit [target] | fix [target]]

Mode: migrate [framework]

Mode: audit [target]

Mode: fix [target]

Install reframe and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews