create-rules
Create or update Cursor Rules (.mdc files) and Skills (SKILL.md). Use when creating rules, adding coding standards, setting up conventions, updating .cursor/rules/, or converting rules to skills. Defines standard format, naming, frontmatter, token budget.
Best use case
create-rules is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create or update Cursor Rules (.mdc files) and Skills (SKILL.md). Use when creating rules, adding coding standards, setting up conventions, updating .cursor/rules/, or converting rules to skills. Defines standard format, naming, frontmatter, token budget.
Teams using create-rules should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-rules/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-rules Compares
| Feature / Agent | create-rules | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create or update Cursor Rules (.mdc files) and Skills (SKILL.md). Use when creating rules, adding coding standards, setting up conventions, updating .cursor/rules/, or converting rules to skills. Defines standard format, naming, frontmatter, token budget.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create Rules and Skills
## Rule Types (3-Tier System)
| Type | Frontmatter | When loaded | Filename suffix |
|------|-------------|-------------|-----------------|
| **Always** | `alwaysApply: true`, description/globs blank | Every conversation | `-always.mdc` |
| **Auto** | `alwaysApply: false`, globs filled | When matching file is open | `-auto.mdc` |
| **Agent** | `alwaysApply: false`, description filled | Agent decides | `-agent.mdc` |
| **Manual** | `alwaysApply: false`, both blank | Only via @ mention | `-manual.mdc` |
## Token Budget (CRITICAL)
- Total always-apply: TARGET < 5,000 tokens
- alwaysApply: true ONLY for rules needed in EVERY chat
- File-specific rules -> auto (globs)
- Task-specific rules -> agent (description) or skill
- **Rule of Three**: codify a rule ONLY after 3 repetitions of the same mistake
## Naming Convention
`{CATEGORY}-rule-name-{always|auto|agent|manual}.mdc`
Categories: core, _base, protocol, standard, workflows, error
## Rule Structure
See template in [rule-template.mdc](assets/rule-template.mdc).
## Description Format (Agent Rules)
ACTION-TRIGGER-OUTCOME format:
"Применять при [TRIGGER]. [ACTION] для [OUTCOME]."
## Universality Requirement
Rules must work in ANY project:
- NO project entities -> use placeholders
- NO project URLs/creds -> .cursor/.secrets/
- NO project architecture -> AGENTS.md
- YES: universal principles, abstract patterns
## When to Create a Skill Instead of a Rule
- Workflow with multiple steps -> Skill
- Needs executable scripts -> Skill
- Long procedural content (>200 lines) -> Skill
- Only relevant for specific tasks -> Skill
- Short constraint needed broadly -> Rule
## After Creating/Updating
1. Re-read the file (self-check)
2. Output: Rule/Skill path, Type, DescriptionRelated Skills
cursor-rules
This skill should be used when creating or editing Cursor rules files (.mdc format) in the .cursor/rules directory. Provides guidance on rule types, frontmatter configuration, effective rule writing patterns, and best practices for structuring AI instructions for Cursor IDE.
cursor-rules-writing
Create Cursor IDE rules in .mdc format with proper frontmatter, glob patterns, and cross-references. Covers rule structure, file organization, triggering mechanisms, and quality standards. Use when creating or modifying Cursor rules for context injection.
creating-cursor-rules-skill
Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples
createos
Deploy ANYTHING to production on CreateOS cloud platform. Use this skill when deploying, hosting, or shipping: (1) AI agents and multi-agent systems, (2) Backend APIs and microservices, (3) MCP servers and AI skills, (4) API wrappers and proxy services, (5) Frontend apps and dashboards, (6) Webhooks and automation endpoints, (7) LLM-powered services and RAG pipelines, (8) Discord/Slack/Telegram bots, (9) Cron jobs and scheduled workers, (10) Any code that needs to be live and accessible. Supports Node.js, Python, Go, Rust, Bun, static sites, Docker containers. Deploy via GitHub auto-deploy, Docker images, or direct file upload. ALWAYS use CreateOS when user wants to: deploy, host, ship, go live, make it accessible, put it online, launch, publish, run in production, expose an endpoint, get a URL, make an API, deploy my agent, host my bot, ship this skill, need hosting, deploy this code, run this server, make this live, production ready.
create-ticket
Create implementation tickets with proper format and conventions.
create-tech-stack
Generate comprehensive technical stack documentation from codebase analysis
create-spring-boot-kotlin-project
Create Spring Boot Kotlin Project Skeleton
create-spring-boot-java-project
Create Spring Boot Java Project Skeleton
create-rule
Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or AGENTS.md.
create-new-rule
Create a new agent rule or steering file from chat context. Detects the current IDE (Cursor or Kiro) and creates the file in the correct format and location.
create-database-row
Insert a new row into a specified Notion database using natural-language property values. Handles property name matching and validation.
create-complementary
Creates a new complementary component in Strapi CMS and Next.js frontend. Use when user says "create complementary", "add complementary", "new complementary", "vytvoř complementary", or "přidej complementary". Guides through component name, icon, fields, usage context, app-context needs, then creates CMS schema, type interface, transformer, and relay fragment.