ワンクリックでManusで任意のスキルを実行

housekeeping

スター35

フォーク0

更新日2026年3月5日 20:09

Organize and modernize AGENTS.md and CLAUDE.md context systems. Use when the user works on structuring, migrating, or curating agent instruction files and repo context architecture.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

bout3fiddy

bout3fiddy/agents

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Housekeeping

Use when work is about organizing or modernizing AGENTS.md/CLAUDE.md context systems.

Key rules

Root AGENTS.md stays concise: critical guardrails, task router, canonical commands, and links.
Domain-heavy guidance lives in nearest scope (apps/frontend/AGENTS.md, infra/AGENTS.md, etc.).
Deep or volatile details go in .agents/repo-context/*, not root AGENTS.md.
Curate continuously: deduplicate, resolve contradictions, remove stale guidance.
Preserve behavior intent during migrations; change structure first, then tighten wording.
Keep AGENTS.md and CLAUDE.md aligned when both exist.

Workflow

Assess current state (concise router vs mixed/legacy monolith).
Migrate content into scoped AGENTS.md files and deep docs.
Rewrite root AGENTS.md as a short router.
Add freshness metadata for volatile facts where feasible.
Verify links/routes and remove conflicting duplicate rules.

Target file tree

repo/
  AGENTS.md                     # concise router + critical guardrails only
  .agents/
    repo-context/
      index.md                  # map of deep guidance
      frontend.md               # detailed frontend runbooks
      infra.md                  # deploy/terraform/release details
      backend.md                # service/runtime/data details
      volatile/
        YYYY-MM-DD-<topic>.md   # time-bounded operational notes
  apps/
    frontend/
      AGENTS.md                 # path-scoped frontend instructions
    agent/
      AGENTS.md                 # path-scoped agent runtime instructions
  infra/
    AGENTS.md                   # path-scoped infra/deploy instructions

Root AGENTS template

# Repo Notes
- What this repo is and major boundaries.
- 5-10 critical guardrails only.
- Task router: where to look for frontend/infra/agent/backend work.
- Canonical commands (build/test/deploy).
- Links to `.agents/repo-context/index.md` and scoped AGENTS files.

Design rules

Root file stays short and high-signal.
Domain-heavy guidance lives in nearest scope.
Volatile operations notes live in .agents/repo-context, not root.
Prefer links over repeated copy.
Resolve contradictions immediately when touched.

Freshness metadata (for volatile notes)

When feasible, add metadata so stale facts are easy to prune:

owner: <team-or-person>
last_verified: YYYY-MM-DD

このリポジトリの他の Skills

同じリポジトリ

zig

bout3fiddy/agents

Performance-first Zig guidance for systems code. Use for Zig speed, allocation, benchmark, batch API, module-readiness, hot-loop, compiler-output, and machine-level performance work. Read the machine-level and benchmarking references first, use compiler/allocation references when the evidence gap needs them, and match the response to the user's request: design discussion, implementation, review, or evidence report.

2026-05-2235

workflows

bout3fiddy/agents

Use for PR review remediation or versioned work package creation/execution. Each workflow has a step-by-step procedure; read it and follow it exactly.

2026-05-1935

coding

bout3fiddy/agents

Performance-grounded code implementation, bug fixes, refactors, code reviews, and technical guidance. Covers hard cutovers, instrumentation, data layout, simple state objects, structured comments, and anti-pattern detection.

2026-05-1835

railway-operations

bout3fiddy/agents

Operate Railway infrastructure: create projects, provision services and databases, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, and query Railway docs. Use this skill whenever the user mentions Railway, deployments, services, environments, build failures, or infrastructure operations, even if they don't say "Railway" explicitly.

2026-03-0635

Housekeeping

Use when work is about organizing or modernizing AGENTS.md/CLAUDE.md context systems.

Key rules

Root AGENTS.md stays concise: critical guardrails, task router, canonical commands, and links.

Domain-heavy guidance lives in nearest scope (apps/frontend/AGENTS.md, infra/AGENTS.md, etc.).

Deep or volatile details go in .agents/repo-context/*, not root AGENTS.md.

Curate continuously: deduplicate, resolve contradictions, remove stale guidance.

Preserve behavior intent during migrations; change structure first, then tighten wording.

Keep AGENTS.md and CLAUDE.md aligned when both exist.

Workflow

Assess current state (concise router vs mixed/legacy monolith).

Migrate content into scoped AGENTS.md files and deep docs.

Rewrite root AGENTS.md as a short router.

Add freshness metadata for volatile facts where feasible.

Verify links/routes and remove conflicting duplicate rules.

Target file tree

repo/ AGENTS.md # concise router + critical guardrails only .agents/ repo-context/ index.md # map of deep guidance frontend.md # detailed frontend runbooks infra.md # deploy/terraform/release details backend.md # service/runtime/data details volatile/ YYYY-MM-DD-<topic>.md # time-bounded operational notes apps/ frontend/ AGENTS.md # path-scoped frontend instructions agent/ AGENTS.md # path-scoped agent runtime instructions infra/ AGENTS.md # path-scoped infra/deploy instructions

Root AGENTS template

# Repo Notes - What this repo is and major boundaries. - 5-10 critical guardrails only. - Task router: where to look for frontend/infra/agent/backend work. - Canonical commands (build/test/deploy). - Links to `.agents/repo-context/index.md` and scoped AGENTS files.

Design rules

Root file stays short and high-signal.

Domain-heavy guidance lives in nearest scope.

Volatile operations notes live in .agents/repo-context, not root.

Prefer links over repeated copy.

Resolve contradictions immediately when touched.

Freshness metadata (for volatile notes)

When feasible, add metadata so stale facts are easy to prune:

owner: <team-or-person> last_verified: YYYY-MM-DD

name	housekeeping
description	Organize and modernize AGENTS.md and CLAUDE.md context systems. Use when the user works on structuring, migrating, or curating agent instruction files and repo context architecture.