We split this skill into the rules it gives an agent

16 rules. About 0 are common, 5 are distinctive, and 11 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 11

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep state in the existing App.tsx-centered flow.

   line 12
2. Very specific:

   Treat server *_sync messages as the source of truth.

   line 13
3. Very specific:

   When a payload or WebSocket shape changes, update both client/src/types.ts and the matching server/ payload usage together.

   line 14
4. Very specific:

   Do not use any. Prefer existing types, unions, and Record shapes.

   line 15
5. Very specific:

   Put styling in client/src/style.css.

   line 16
6. Very specific:

   Add new components under client/src/components/ as PascalCase.tsx files with named exports.

   line 17
7. Distinctive:

   Read the relevant component, hook, type definitions, and matching server handler before editing.

   line 21
8. Distinctive:

   If the change touches messages or payloads, trace the matching server path and update both sides together.

   line 22
9. Very specific:

   If styles change, extend client/src/style.css rather than scattering styles across files.

   line 24
10. Distinctive:

    If the UI changed, start the app and verify the main interaction path in the browser before considering the task done.

    line 32
11. Very specific:

    Use todome-type-lint-runner when you mainly need a compact report from frontend tsc and lint.

    line 36
12. Very specific:

    Use vercel-react-best-practices when the change involves React performance or rendering behavior.

    line 37
13. Very specific:

    Use vercel-composition-patterns when the component API is drifting toward boolean-prop sprawl.

    line 38
14. Very specific:

    Use vercel-react-view-transitions only when the task explicitly involves view transitions or state-change animation.

    line 39
15. Distinctive:

    Keep recommendations and edits concrete and repo-specific.

    line 43
16. Distinctive:

    Prefer small diffs that preserve the existing visual language and data flow.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.