agentleFS
Sign inStart free
OlliTapioOlliTapio/claude_skills/skills/setup-project/SKILL.md

setup-project

Skill0 starsChanged 17 days agoMITView on GitHub

Scaffold a new project end-to-end — pick an LLM-friendly language, lay out the layered architecture (controllers/services/repos/views), install .claude rules, and wire quality gates. Use when starting a new repo, bootstrapping a project, or standardizing an existing one's structure and guardrails.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research, implement and 3 more.

Other files people use alongside this one.

Files 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.
  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create the directories and one working slice (controller → service → repo → view).

    line 26
  2. Very specific:

    Add project-specific rules with the rule-authoring skill (testing, API design, naming).

    line 31
  3. Very specific:

    Run the quality-gates skill: per-language checks, then git pre-commit (fast) + pre-push (slow) hooks.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 18 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

setup-project

1. Choose the language

Recommend the language the model codes most reliably for the domain (favor static typing plus mature formatter/linter/test tooling). Confirm with the user before scaffolding.

2. Scaffold the layered architecture

Four layers, dependencies pointing one way: controllers → services → repos, with views for output.

src/
  controllers/   entry points (HTTP/CLI/queue): validate input, call one service, map through a view
  services/      business logic & orchestration; storage/transport-agnostic
  repos/         data access (DB, external APIs); returns domain types
  views/         output shaping (DTOs, serializers, templates, UI)
  domain/        shared types/entities
tests/

Create the directories and one working slice (controller → service → repo → view). Match the language's idioms.

3. Install .claude rules

  • Copy ../../templates/rules/layered-architecture.md (relative to this skill's base directory) into .claude/rules/ — enforces layer responsibilities and dependency direction.
  • Add project-specific rules with the rule-authoring skill (testing, API design, naming).

4. Wire quality gates

Run the quality-gates skill: per-language checks, then git pre-commit (fast) + pre-push (slow) hooks.

5. Verify

Confirm the sample slice builds/tests green, the hooks pass on a clean tree and fail on an injected smell, and .claude/rules/ loads (edit a file under src/ and check the rule applies).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free