follow-workspace-rules
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: follow-workspace-rules
description: Aligns code with this repository's Cursor rules in `.cursor/rules/` (layered architecture, namin…
category: ai
runtime: no special runtime
---
# follow-workspace-rules output preview
## PART A: Task fit
- Use case: Aligns code with this repository's Cursor rules in `.cursor/rules/` (layered architecture, naming, styling, performance, anti-patterns). Use when implementing or refactoring features, reviewing diffs, fixing lint or convention issues, or when the user asks to follow project standards, workspace rules, or AGENTS.md. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Source of truth / Rule map (what to read when) / Workflow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Aligns code with this repository's Cursor rules in `.cursor/rules/` (layered architecture, naming, styling, performance, anti-patterns). Use when implementing or refactoring features, reviewing diffs, fixing lint or convention issues, or when the user asks to follow project standards, workspace rules, or AGENTS.md. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Source of truth / Rule map (what to read when) / Workflow” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Source of truth / Rule map (what to read when) / Workflow”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: follow-workspace-rules
description: Aligns code with this repository's Cursor rules in `.cursor/rules/` (layered architecture, namin…
category: ai
source: tomevault-io/skills-registry
---
# follow-workspace-rules
## When to use
- Aligns code with this repository's Cursor rules in `.cursor/rules/` (layered architecture, naming, styling, performanc…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Source of truth / Rule map (what to read when) / Workflow” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "follow-workspace-rules" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Source of truth / Rule map (what to read when) / Workflow
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Follow workspace rules
Source of truth
Project conventions live in .cursor/rules/*.mdc (always applied in Cursor). Do not rely on memory alone—open and follow the relevant .mdc file when the task touches that area.
Also heed AGENTS.md (Next.js: consult node_modules/next/dist/docs/ before using framework APIs you are unsure about).
Rule map (what to read when)
| File | Use when |
|---|---|
architecture.mdc |
Deciding where new code belongs; import direction (App → Features → Lib/Components); feature public API via index.ts |
layers.mdc |
Placing or reviewing code under src/app/, src/features/, src/components/, or src/lib/ |
naming.mdc |
New files, folders, hooks, services, tests |
styling.mdc |
Tailwind/cn(), NavLink, design tokens, globals.css utilities |
anti-patterns.mdc |
Quick pass for common violations (duplicate link styling, wrong layer imports, hook misuse, etc.) |
performance.mdc |
State placement, lists, memoization, context providers |
Repo path (for search/open): .cursor/rules/<file>.
Workflow
- Classify the change: Which layers and files are involved (
app,features,components,lib)? - Pull in rules: At minimum, skim
architecture.mdc+layers.mdcfor anything that adds imports or new modules. Addstyling.mdcfor UI;naming.mdcfor new files;performance.mdcwhen changing state, context, or large lists. - Implement so that:
- Dependency flow matches the architecture table (no upward imports; no feature-to-feature imports;
libstays free of feature/component imports). - UI matches styling rules (
NavLinkfor links,cn()for conditional classes, tokens fromtailwind.config.js/ globals—not ad-hoc patterns that break safelisting).
- Dependency flow matches the architecture table (no upward imports; no feature-to-feature imports;
- Before finishing: Re-read
anti-patterns.mdcfor a fast sanity check on the touched surface.
Conflict resolution
If a suggestion conflicts with .cursor/rules, the rules win. If two rules seem to conflict, prefer architecture / layers for structure, then styling and anti-patterns for UI and React habits.
Relation to other project skills
ui-design-reviewfocuses on visual quality and hierarchy; this skill covers repository-wide conventions (layers, naming, Tailwind/NavLink rules, performance guardrails). Use both when polishing UI that must also match project standards.
Source: andraderaul/random-fy — distributed by TomeVault.
Decide Fit First
.cursor/rules/(layered architecture, naming, styling, performance, anti-pa…Design Intent
How To Use It
Boundaries And Review