.cursor/skills/overview/SKILL.md
Creates or updates docs/overview.md — the project's purpose and background. Load when starting a new project, when the project's goals or context have changed, or when docs/overview.md does not exist. Covers what to write, what to omit, and how to keep the document agent-friendly.
npx skillsauth add poko8nada/portfolio-v3 overviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Captures the irreducible knowledge that cannot be derived from code, tests, or ADRs — the why and why-not behind the project's existence. Agents use it to understand intent when making architectural decisions.
Do not use overview as a substitute for behavior or ADR.
Expected behavior per feature belongs in docs/behavior.md.
Decision trade-offs and rejected alternatives belong in docs/adr/*.md.
Write this document in Japanese.
---
last-validated: YYYY-MM-DD
phase: current
---
# [プロジェクト名]
## Problem
[1〜3文:どんな問題を、誰のために解決するか]
## Goals
- [具体的・測定可能なゴール]
## Non-goals
- [対象外にしていること、およびその理由]
## Constraints
- [外部制約:法律・SLA・組織ポリシーなど]
## Tech Stack Rationale
- [選択したもの]:[なぜ他の選択肢でなくこれか] → see ADR-NNNN
Update last-validated whenever you verify the document still reflects reality.
If any section no longer holds, update it or supersede with a new version.
A stale last-validated is a signal the document may have drifted.
documentation
Creates or updates docs/spec.md — the project's functional requirements. Load when defining new features, when requirements have changed, or when docs/spec.md does not exist. Covers what to write, what to omit, and how to express requirements in a way that is verifiable and agent-friendly.
development
Bootstraps project documentation for an existing repository by reading the codebase, README, tests, and package metadata, then creates or updates docs/overview.md, docs/spec.md, and ADRs when significant architectural decisions are discovered. Use when asked to document a repo, extract project purpose, write overview/spec docs, review an existing codebase, or capture architecture decisions from source.
development
Creates or updates docs/overview.md — the project's purpose and background. Load when starting a new project, when the project's goals or context have changed, or when docs/overview.md does not exist. Covers what to write, what to omit, and how to keep the document agent-friendly.
documentation
Implements a new feature using docs-first delivery, boundary-driven structure, and skeleton-first execution. Load when adding a route, feature, or new user-visible behavior.