File Organization

Good project structure prevents the chaos that inevitably hits around month three when nobody can find anything. This gives you opinionated templates for React/Next.js frontends and Node.js backends, along with naming conventions that actually make sense (PascalCase for components, kebab-case for folders, is/has/can prefixes for booleans). The constraint on five levels of folder depth is smart because deeply nested structures are where good intentions go to die. It covers the basics like path aliases, barrel exports, and avoiding circular dependencies. Not revolutionary, but having these patterns codified means less bikeshedding in PRs about where files should live.

Install to Claude Code

npx -y skills add supercent-io/skills-template --skill file-organization --agent claude-code