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.
npx agentmods add rules/bmoff/code-first-design/code-first-design-promotegit clone --depth 1 https://github.com/bmoff/code-first-designWhat 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.
| Model | Per session | Once 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 |
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.
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
/protofor 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
-
Move
components/draft/<Name>.tsx→components/<Name>.tsx(or feature folder likecomponents/<feature-name>/<Name>.tsx). -
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)
-
If the component should appear in the design system (recommended for reusable components):
- In
app/proto/_ds/registry.ts, add entry tocustomComponents: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} />, };
- In
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.
- yesterday First seen · 77 lines · 0 tokens per session scan A 0941c01cdbeb
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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.