code-first-design-promote

A procedure for moving a finished UI component from a draft area into the production component library. A component is a reusable piece of an interface, while a prototype is an experimental screen or flow.

In plain words
What is it for?
Use it when a specific draft component is ready for production, including deciding whether it should be registered in the project's design system.
Why use it?
It prevents experimental code from being treated as production code and ensures references and component listings are updated correctly.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/bmoff/code-first-design/code-first-design-promote
Clone the repo
git clone --depth 1 https://github.com/bmoff/code-first-design

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00817
Opus 5 $0.00000 $0.00409
Sonnet 5 $0.00000 $0.00163
Haiku 4.5 $0.00000 $0.00082

Measured yesterday against content hash 0941c01cdbeb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-first-design-promote scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/code-first-design-promote.mdc · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Promoting components

Before you start: Read code-first-design.mdc to understand how the framework works, especially the "Draft vs production" and "Components vs prototypes" sections.

⚠️ IMPORTANT:

  • You promote components, not prototypes. Prototypes stay in /proto for ongoing experimentation.
  • If you have components within a prototype that you want to use in production, promote those individual components.
  • Confirm which component to promote before starting. Ask: "Which component should I promote to production?" Only proceed once you have a clear answer.
  • Decide if the component should appear in the design system: If it's a reusable component that others should discover, register it. If it's only used within a specific prototype/feature, you can skip registration (but still move it to production).

Steps

  1. Move components/draft/<Name>.tsxcomponents/<Name>.tsx (or feature folder like components/<feature-name>/<Name>.tsx).

  2. Update imports everywhere:

    • Update imports in any files that use this component (prototypes, other components, etc.)
    • Update imports in app/proto/_ds/component-registry.ts (if component is registered there)
    • Update imports in app/proto/components/[slug]/page.tsx (if component has a demo)
  3. If the component should appear in the design system (recommended for reusable components):

    • In app/proto/_ds/registry.ts, add entry to customComponents:
      customComponents: [
        { 
          name: "<Name>", 
          path: "/proto/components/<kebab-name>", 
          file: "components/<Name>.tsx"  // or "components/<feature-name>/<Name>.tsx"
        }
      ]
      
    • If it was previously in draftComponents, remove it from there.
    • In app/proto/_ds/component-registry.ts, update the import and config:
      import { <Name> } from '@/components/<Name>';  // Updated path
      import { defaultProps } from '@/components/<Name>';
      // If in feature folder:
      // import { <Name> } from '@/components/<feature-name>/<Name>';
      // import { defaultProps } from '@/components/<feature-name>/<Name>';
      
      export const COMPONENT_CONFIGS: Record<string, ComponentDemoConfig> = {
        '<kebab-name>': {
          componentName: '<Name>',
          component: <Name>,
          defaultProps: defaultProps,
          fallbackMessage: '<Name> failed to render.',
        },
      };
      
    • In app/proto/components/[slug]/page.tsx, update the import and demo:
      import { <Name> } from '@/components/<Name>';  // Updated path
      import { defaultProps } from '@/components/<Name>';
      // If in feature folder:
      // import { <Name> } from '@/components/<feature-name>/<Name>';
      // import { defaultProps } from '@/components/<feature-name>/<Name>';
      
      const COMPONENT_DEMOS: Record<string, () => React.ReactElement> = {
        '<kebab-name>': () => <Name {...defaultProps} />,
      };
      

Read the full file on GitHub · 77 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 77 lines · 0 tokens per session scan A 0941c01cdbeb

Subscribe to this mod's changes

code-first-design-promote is a cursor rule published in the GitHub repository bmoff/code-first-design (4 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 817 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.