一键在 Manus 中运行任何 Skill

repo-folder-structure

星标4

分支1

更新时间2026年5月6日 18:27

Defines hybrid feature-based frontend layout under src plus backend controllers-services-data layering and HTTP flow direction. Applies when creating routes, pages, features, or backend modules for consistency. Do not use for monorepo-wide policies outside this template or frameworks that forbid this layout.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

rodrigobranas

rodrigobranas/f_ia_m1_3

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Repository folder structure

Procedures

When adding frontend React assets

Colocate artifacts that change together: component implementations, narrowly scoped styles, companion tests, and feature-local typings.
Place product-domain UI under src/features/<feature-name>/ with subfolders (components, hooks, optional lib, api, types), exporting public surfaces via a selective index.ts barrel when required.
Keep shared primitives and design-system elements under src/components/ui and sibling global reusable components without embedding domain rules inside primitive layers.
Keep cross-feature hooks under src/hooks; keep generic helpers under src/lib.
Assemble routed experiences under src/pages; define route tables under src/routes; keep bootstrap concerns under src/app alongside main.tsx and global styles (index.css).
Avoid gratuitous nesting beyond roughly three levels; prefer baseUrl/path aliases declared in TypeScript configs for readability.
Read references/repo-layout.md for the canonical ASCII tree snapshot and anti-pattern callouts whenever placement is ambiguous.

When extending backend modules

Respect the dependency direction HTTP → controllers/ → services/ → data/; controllers marshal HTTP shapes and statuses, services encapsulate orchestration and domain guards, data modules perform persistence and integrations.
Keep handlers in controllers/, workflows in services/, adapters in data/ (repositories, clients, shared external SDK boundaries).
Share cross-layer schemas or validation artifacts under neutral folders (src/schemas, src/types) avoiding import cycles violating the layering arrow.

Error Handling

When new HTTP calls emerge inside UI primitives, relocate them behind features/<name>/api or centralized HTTP clients referenced in references/repo-layout.md.
When backend logic leaks framing details into controllers, refactor transport mapping upward and domain rules downward per the layered flow diagram inside references/repo-layout.md.

同仓库更多 Skills

同仓库

code-standards-en

rodrigobranas/f_ia_m1_3

Specifies English identifiers, casing conventions, verb-led functions, parameterized objects over long arg lists, CQS separation, guarded early returns, split boolean-flag behaviors, sizing limits for methods and classes, minimal comments. Do not use when localized naming is required by product policy.

2026-05-064

express-rest-http

rodrigobranas/f_ia_m1_3

Maps Express endpoints to REST-ish resources with POST action verbs for mutations, mandatory security middleware, canonical status codes, OpenAPI documentation, pagination limit and offset, partial field queries, native fetch for outbound HTTP. Do not use when replacing Express with another server framework.

2026-05-064

nodejs-typescript-conventions

rodrigobranas/f_ia_m1_3

Enforces TypeScript-only source, npm for scripts and deps, ESM import and export defaults, async await over raw then chains, no any types, minimal let usage, private or readonly class fields, functional collection helpers. Do not use for plain JavaScript codebases or non-npm package managers.

2026-05-064

react-frontend-conventions

rodrigobranas/f_ia_m1_3

Constrains functional React with TypeScript and Tailwind: local state colocation, explicit props instead of spreads, Context for cross-cutting state, useMemo for heavy derivations, use-prefixed hooks, component tests. Do not use for class components, styled-components, or non-Tailwind styling stacks.

2026-05-064

skill-best-practices

rodrigobranas/f_ia_m1_3

Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.

2026-05-064

vitest-testing

rodrigobranas/f_ia_m1_3

Guides Vitest-based unit and integration tests with vi mocks, Arrange-Act-Assert, fake timers for Date, HTTP endpoint integration tests without supertest, use-case and domain coverage. Do not use for Jest-centric projects or Sinon as primary mocking.

2026-05-064

name	repo-folder-structure
description	Defines hybrid feature-based frontend layout under src plus backend controllers-services-data layering and HTTP flow direction. Applies when creating routes, pages, features, or backend modules for consistency. Do not use for monorepo-wide policies outside this template or frameworks that forbid this layout.

Repository folder structure

Procedures

When adding frontend React assets

Colocate artifacts that change together: component implementations, narrowly scoped styles, companion tests, and feature-local typings.
Place product-domain UI under src/features/<feature-name>/ with subfolders (components, hooks, optional lib, api, types), exporting public surfaces via a selective index.ts barrel when required.
Keep shared primitives and design-system elements under src/components/ui and sibling global reusable components without embedding domain rules inside primitive layers.
Keep cross-feature hooks under src/hooks; keep generic helpers under src/lib.
Assemble routed experiences under src/pages; define route tables under src/routes; keep bootstrap concerns under src/app alongside main.tsx and global styles (index.css).
Avoid gratuitous nesting beyond roughly three levels; prefer baseUrl/path aliases declared in TypeScript configs for readability.
Read references/repo-layout.md for the canonical ASCII tree snapshot and anti-pattern callouts whenever placement is ambiguous.

When extending backend modules

Respect the dependency direction HTTP → controllers/ → services/ → data/; controllers marshal HTTP shapes and statuses, services encapsulate orchestration and domain guards, data modules perform persistence and integrations.
Keep handlers in controllers/, workflows in services/, adapters in data/ (repositories, clients, shared external SDK boundaries).
Share cross-layer schemas or validation artifacts under neutral folders (src/schemas, src/types) avoiding import cycles violating the layering arrow.

Error Handling

When new HTTP calls emerge inside UI primitives, relocate them behind features/<name>/api or centralized HTTP clients referenced in references/repo-layout.md.
When backend logic leaks framing details into controllers, refactor transport mapping upward and domain rules downward per the layered flow diagram inside references/repo-layout.md.