agentleFS
Sign inStart free
psubramanianpsubramanian/Claude-Skills/project-structure/SKILL.md

project-structure

Skill0 starsChanged 7 months agoNo licenceView on GitHub

Establish consistent, scalable folder organization and naming conventions for Next.js SaaS applications. TRIGGER this skill automatically when the user mentions: project setup, folder structure, where to put files, file organization, naming conventions, starting a new Next.js project, "where should I create this", "how should I organize", scaffolding, monorepo, directory layout, or any question about where code belongs. Also trigger at the start of a new feature to guide consistent file placement.

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — 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 14 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 versions20 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 20

    1. modelcontextprotocol/servers★ 92ksame name
    2. microsoft/agent-framework★ 14ksame name
    3. elie222/inbox-zero★ 13ksame name
    4. modelcontextprotocol/inspector★ 11ksame name
    5. enso-org/enso★ 7.4ksame name
    6. steipete/agent-scripts★ 7.4ksame name
    7. trezor/trezor-suite★ 1.1ksame name
    8. spiriMirror/libuipc★ 336same name
    9. Resgrid/Core★ 229same name
    10. tomo3141592653/ayumu-oss★ 9same name

    10 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 native-nostalgia-stack, roadmap-review and 5 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.
    • frostneySkill

      native-nostalgia-stack

      Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.

      Also in 3 projects that use this

    • frostneySkill

      roadmap-review

      Reviews a roadmap from fresh project evidence and produces a verified, throughput-anchored version plan, with execution gated on confirmation. Use when reviewing a roadmap, planning releases, or sequencing a backlog.

      Also in 3 projects that use this

    • MicrosoftSkill

      update-pr

      Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.

      Also in 3 projects that use this

    • ReinaMacCredySkill

      codebase-audit

      Deep codebase audit that first reads project docs (AGENTS.md, README.md) and investigates the architecture, then systematically finds hardcoded constants that should be dynamic and unfinished code (TODOs, "will"/"would" in comments). Use this skill when the user wants a thorough code review for hygiene issues, asks to find hardcoded values, wants to audit for TODOs or incomplete code, says things like "audit this codebase", "find hardcoded stuff", "what's unfinished", "find tech debt", "code hygiene check", or asks you to look across the whole project for issues. Also use when the user asks to understand a project before making changes, or wants a comprehensive health check of their codebase.

      Also in 3 projects that use this

    • sahinSkill

      create-issue

      Also in 3 projects that use this

    • SentrySkill

      create-pr

      Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

      Also in 4 projects that use this

    • +1 more from frostney
  • In this repository20 other files it gives its agents.

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