poko8nada/overview
.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.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add poko8nada/corp_site-type01 overviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 11:07 PM8.5s1 file scanned
SKILL.md
- name:
- overview
- description:
- >
Project Overview
Purpose of docs/overview.md
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.
What to write
- Problem: What problem does this project solve? For whom?
- Goals: What does success look like?
- Non-goals: What is explicitly out of scope, and why?
- Constraints: External constraints (legal, organizational, SLA, third-party).
- Tech Stack Rationale: Why this tech stack over alternatives? Link to ADRs for details.
What NOT to write
- Current system state — code and tests are the source of truth
- Directory structure — agents can read the filesystem
- How features work — that belongs in code and tests
- Anything that will change as implementation evolves
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.
Format
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
Maintenance rule
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.
Related Skills
poko8nada/project-doc-bootstrap
development
VerifiedTrustedCommunity
Bootstraps project documentation for an existing repository by reading the codebase, README, tests, and package metadata, then creates or updates docs/overview.md, docs/behavior.md, and ADRs when significant architectural decisions are discovered. Use when asked to document a repo, extract project purpose, write overview/behavior docs, review an existing codebase, or capture architecture decisions from source.
SKILL.mdUpdated Apr 16, 2026
poko8nada/new-feature
documentation
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 16, 2026
poko8nada/issue
tools
VerifiedTrustedCommunity
Manages GitHub Issues using gh CLI — creation, decomposition, update, and close. Load when asked to create a new issue, break down a large task into issues, update issue status or labels, or close an issue after a PR is merged. Human decides whether to create an issue. Agent handles all gh CLI operations.
SKILL.mdUpdated Apr 16, 2026
poko8nada/grill-me
development
VerifiedTrustedCommunity
When creating or refining ideas, ask the user detailed questions until a shared understanding is reached, and work through each branch of the decision tree one by one. Use this approach if you want to be rigorously questioned about an idea, or if you’ve specifically asked to be “grill me.”.
SKILL.mdUpdated Apr 16, 2026