poko8nada/overview
.github/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.
$ install --global
skillsauthnpx skillsauth add poko8nada/pj_docs 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, 5:20 PM42.2s1 file scanned
SKILL.md
- name:
- overview
- description:
- >
Project Overview
Purpose of docs/overview.md
This document 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).
- Key decisions: 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
Format
This document should be written in Japanese.
---
last-validated: YYYY-MM-DD
phase: current
---
# [Project Name]
## Problem
[1-3 sentences: what problem, for whom]
## Goals
- [Specific, measurable goal]
- [Specific, measurable goal]
## Non-goals
- [What is out of scope and why]
## Constraints
- [External constraint: legal, SLA, org policy, etc.]
## Tech Stack Rationale
- [Choice]: [Why this over alternatives] → 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 rotted.
Related Skills
poko8nada/planning-project
tools
VerifiedTrustedCommunity
Composite Skill. This skill is used for project planning. Users request that a project plan be created, particularly during the initial stages.
1SKILL.mdUpdated Apr 16, 2026
poko8nada/planning-doc-creation
documentation
VerifiedTrustedCommunity
Core Skill. This skill is for document creation. User ask you to create planning documents, such as requirement and task breakdown.
1SKILL.mdUpdated Apr 16, 2026
poko8nada/nextjs-architecture
development
VerifiedTrustedCommunity
Core Skill. Next.js 15+ App Router architecture guidelines including component patterns, state management with Zustand, server actions, and project structure. Use when developing Next.js applications.
1SKILL.mdUpdated Apr 16, 2026
poko8nada/honox-architecture
development
VerifiedTrustedCommunity
Core Skill. HonoX architecture guidelines including file-based routing, Islands pattern, component types, performance optimization, and best practices for full-stack development.
1SKILL.mdUpdated Apr 16, 2026