wp-agent-mcp / rules
Cursor rule1 starsChanged 33 days agoMITView on GitHub
WordPress-specific heuristics for identifying blocks/patterns/templates and variant mechanisms generically.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- .cursor/rules/00-project-overview.mdcCursor rule
- .cursor/rules/10-architecture-and-safety.mdcCursor rule
- .cursor/rules/20-indexing-and-audit-contracts.mdcCursor rule
- .cursor/rules/30-mcp-implementation-guidelines.mdcCursor rule
- wp-agent-toolkit-bootstrapSkill
- wp-agent-toolkit-cursor-pluginSkill
- wp-agent-toolkit-demoSkill
- wp-agent-toolkit-design-bridgeSkill
- wp-agent-toolkit-mcp-serverSkill
- wp-agent-toolkit-orchestratorSkill
- wp-agent-toolkit-wp-helper-pluginSkill
The file
We split this 40-wp-introspection-guidelines.mdc into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If the user asks about active theme tokens, helpers, or design system details, use get_theme_profile.
- Very specific: line 26
Before creating new presentation code from a mock, run the design bridge workflow and reconcile tokens against get_theme_profile / bridge …
- Distinctive: line 27
Never paste raw Figma hex, px spacing, or font stacks into theme files when preset CSS variables exist.
- Very specific: line 30
When suggesting reuse/extend/create, include:
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
--- description: WordPress-specific heuristics for identifying blocks/patterns/templates and variant mechanisms generically. globs: "**/*.php,**/*.html,**/*.json,**/*.js,**/*.ts,**/*.css,**/*.scss" alwaysApply: false --- # WP Introspection (Generic Component Rules) ## Component surfaces to scan - Runtime: registered blocks, styles, variations (if helper plugin installed) - Files: block.json, patterns, templates, template parts, partials/components, CSS/JS - Content DB: post_content block markup, known builder meta (best-effort) ## Intent-based theme routing - If the user asks about active theme tokens, helpers, or design system details, use `get_theme_profile`. ## Variant mechanisms (generic) - block styles (is-style-*) - block variations - pattern variants (multiple similar patterns) - template part variants (header-compact, footer-legal) - CSS modifiers (component--compact, is-variant-x) - theme mods/options controlling rendering ## Design bridge (Figma / screenshot → repo conventions) - Before creating new presentation code from a mock, run the design bridge workflow and reconcile tokens against `get_theme_profile` / bridge output. - Never paste raw Figma hex, px spacing, or font stacks into theme files when preset CSS variables exist. ## Always output "why" When suggesting reuse/extend/create, include: - what exists - where it lives - how enabled - why the recommended mechanism matches project conventions
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.