follow workspace rules
- Repo stars 0
- Author repo skills-registry
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- 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 explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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`](../../rules/architecture.mdc) | Deciding where new code belongs; import direction (`App → Features → Lib/Components`); feature public API via `index.ts` |
| [`layers.mdc`](../../rules/layers.mdc) | Placing or reviewing code under `src/app/`, `src/features/`, `src/components/`, or `src/lib/` |
| [`naming.mdc`](../../rules/naming.mdc) | New files, folders, hooks, services, tests |
| [`styling.mdc`](../../rules/styling.mdc) | Tailwind/`cn()`, `NavLink`, design tokens, `globals.css` utilities |
| [`anti-patterns.mdc`](../../rules/anti-patterns.mdc) | Quick pass for common violations (duplicate link styling, wrong layer imports, hook misuse, etc.) |
| [`performance.mdc`](../../rules/performance.mdc) | State placement, lists, memoization, context providers |
Repo path (for search/open): `.cursor/rules/<file>`.
## Workflow
1. **Classify the change**: Which layers and files are involved (`app`, `features`, `components`, `lib`)?
2. **Pull in rules**: At minimum, skim `architecture.mdc` + `layers.mdc` for anything that adds imports or new modules. Add `styling.mdc` for UI; `naming.mdc` for new files; `performance.mdc` when changing state, context, or large lists.
3. **Implement** so that:
- Dependency flow matches the architecture table (no upward imports; no feature-to-feature imports; `lib` stays free of feature/component imports).
- UI matches styling rules (`NavLink` for links, `cn()` for conditional classes, tokens from `tailwind.config.js` / globals—not ad-hoc patterns that break safelisting).
4. **Before finishing**: Re-read `anti-patterns.mdc` for 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-review`](../ui-design-review/SKILL.md)** focuses 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](https://github.com/andraderaul/random-fy) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Sections and files
Listed in source order.
sections -> Source of truth → Rule map (what to read when) → Workflow → Conflict resolution → Relation to other project skills
terms -> (always applied in Cursor). Do not rely on memory alone— · AGENTS.md · Classify the change · Pull in rules · Implement · Before finishing · .cursor/rules · architecture / layers
files/cmd -> .cursor/rules/*.mdc · .mdc · AGENTS.md · node_modules/next/dist/docs/ · architecture.mdc · App → Features → Lib/Components · index.ts · layers.mdc
body sha256 -> c5161da9e665
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.mdcfile when the task touches that area. Also heedAGENTS.md(Next.js: consultnode_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 viaindex.tslayers.mdc· Placing or reviewing code undersrc/app/,src/features/,src/components/, orsrc/lib/naming.mdc· New files, folders, hooks, services, testsstyling.mdc· Tailwind/cn(),NavLink, design tokens,globals.cssutilitiesWorkflow
Classify the change: Which layers and files are involved (
app,features,components,lib)? Pull in rules: At minimum, skimarchitecture.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).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.