write-tests

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

• 0

  Common

  Most of the 65 edited versions we read keep these.

• 0

  Distinctive

  This author's own choices. Worth a look.

• 1

  Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 65 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

• Other versions69 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 69

  1. remix-run/remix★ 33ksame name
  2. getsentry/sentry-javascript★ 8.8ksame name
  3. dzhng/jevgrep★ 3.1ksame name
  4. meta-pytorch/OpenEnv★ 2.8ksame name
  5. huggingface/OpenEnv★ 2.8ksame name
  6. JamieMason/syncpack★ 2.1ksame name
  7. dzhng/skills★ 1.4ksame name
  8. clice-io/clice★ 1.4ksame name
  9. ryokun6/ryos★ 1.3ksame name
  10. openfootmanager/openfootmanager★ 1.2ksame name

  59 more not listed

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Used alongsideProjects with it also use close-spec, design-with-images and 10 more.

  Other files people use alongside this one.

  How we pick theseFiles found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 5 projects that use this

  • LucasMatuszewskiSkill

    audit-agents

    Audit and maintain agent configuration files (.claude/agents, AGENTS.md, CLAUDE.md, agent-memory). Checks for duplicates, outdated info, naming conflicts, wrong technical facts, and files over 200 lines. Fixes all issues and commits.

    Also in 5 projects that use this

  • wolverin0Skill

    audit-decisions

    Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

    Also in 4 projects that use this

  • rhnfzlSkill

    explore-unknowns

    Walk the user through mapping the unknowns of a task before, during, and after they build it, and hand them a four-quadrant map (settled ground, open decisions, taste, and landmines) they keep. Reach for this eagerly whenever a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, a build-queue or architecture-changing task is about to start, a mid-build deviation needs capturing, or a finished change needs buy-in or verified understanding before merge. Trigger even when the skill is not named: "do a blindspot pass", "find my unknown unknowns", "interview me about this change", "brainstorm the approach for a task I am about to build", "help me scope this", "what am I missing here", "plan this before I build", "I know nothing about X in this codebase". When a territory profile is present it reads memory and the graph first and feeds the map into the build pipeline; without one it degrades to a plain general map. Not for trivial or mechanical tasks with clear acceptance criteria, single-fact lookups, pure debugging of a known symptom, or pure code review, those have their own tools. Do not use it to run the build itself; the map is the deliverable and implementation remains a separate task, whether it has not started or is already underway.

    Also in 5 projects that use this

  • +5 more from dzhng
• In this repository35 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • .cursor/rules/e2e-testing.mdcCursor rule
  • .cursor/rules/features/cleaner.mdcCursor rule
  • .cursor/rules/features/delayed-actions.mdcCursor rule
  • .cursor/rules/features/digest.mdcCursor rule
  • .cursor/rules/features/knowledge.mdcCursor rule
  • .cursor/rules/features/reply-memory.mdcCursor rule
  • .cursor/rules/features/schedule.mdcCursor rule
  • .cursor/rules/posthog-feature-flags.mdcCursor rule
  • .cursor/rules/task-list.mdcCursor rule
  • .cursor/rules/ultracite.mdcCursor rule
  • agent-browserSkill
  • changelogSkill
  • cloud-dev-environmentSkill
  • code-simplifierSkill
  • create-prSkill
  • e2eSkill
  • environment-variablesSkill
  • explain-changesSkill
  • fullstack-workflowSkill
  • llmSkill
  • llm-testSkill
  • loggingSkill
  • prismaSkill
  • project-structureSkill
  • pr-watchSkill
  • qa-labelSkill
  • review-ai-prompt-changesSkill
  • reviewSkill
  • test-featureSkill
  • testingSkill
  • ui-componentsSkill
  • update-packagesSkill
  • waitSkill