Architecture Guidelines
eser/stack
System design in eserstack: double-layered hexagonal architecture, explicit adapter composition, public API and CLI surface, request metadata, testing strategy, ADRs.
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies.
Install Technical Specification
$ npx skills add secondsky/claude-skills --skill technical-specification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install secondsky/claude-skills technical-specification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .claude/skills/technical-specification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .claude/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add secondsky/claude-skills --skill technical-specification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install secondsky/claude-skills technical-specification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .agents/skills/technical-specification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .agents/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add secondsky/claude-skills --skill technical-specification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install secondsky/claude-skills technical-specification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .cursor/skills/technical-specification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .cursor/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/secondsky/claude-skills.git --path plugins/technical-specification/skills/technical-specification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add secondsky/claude-skills --skill technical-specification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install secondsky/claude-skills technical-specification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .gemini/skills/technical-specification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .gemini/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install secondsky/claude-skills technical-specificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add secondsky/claude-skills --skill technical-specification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .github/skills/technical-specification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .github/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add secondsky/claude-skills --skill technical-specification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install secondsky/claude-skills technical-specification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/secondsky/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/technical-specification/skills/technical-specification .opencode/skills/technical-specification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "technical-specification" agent skill from https://github.com/secondsky/claude-skills/tree/main/plugins/technical-specification/skills/technical-specification into .opencode/skills/technical-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "technical-specification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
technical-specification- GitHub stars
- 227
- Token cost
- ~754 tokens
- SKILL.md length
- 78 words
- Files
- 2 (incl. references)
- Skills in repo
- 169
- Repo updated
- First seen
- Licence
- MIT
At a glance
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies.
- Planning features
- SKILL.md covers Specification Template, Implementation Plan, Testing Strategy and Risks & Mitigations, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Documenting system design
What it does
Technical Specification is an agent skill from secondsky/claude-skills. Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/template.md`).
It sits in Development, covering Test strategy and Architecture decision records. The repository describes itself as: Production-ready skills for Claude Code CLI - Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.
When your agent uses it
- Planning features
- Documenting system design
- Creating architecture decision records
Example prompts
- “Use the technical-specification skill to create detailed technical specifications for software projects covering requirements, architecture, APIs…”
- “/technical-specification”
What it can do on your machine
Read from SKILL.md and the folder at commit 8837836. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Technical Specification loads about 754 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 78 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from secondsky/claude-skills at commit 8837836, republished under its MIT licence (© secondsky). 78 words, ~754 tokens.
Download SKILL.mdSave it as
.claude/skills/technical-specification/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- technical-specification
- description
- Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
- license
- MIT
Technical Specification
Create comprehensive technical specifications for software projects.
Specification Template
# Technical Specification: [Feature Name]
## Metadata
- **Status**: Draft | In Review | Approved
- **Author**: [Name]
- **Reviewers**: [Names]
- **Last Updated**: [Date]
## Executive Summary
[2-3 sentences: What problem does this solve? What's the proposed solution?]
## Background & Context
- Current pain points
- Why now?
- Related work
## Goals
### Primary Goals
1. [Measurable goal]
### Non-Goals
- [What this spec explicitly does NOT cover]
## Functional Requirements
| ID | Requirement | Priority |
|----|-------------|----------|
| FR-1 | [Description] | P0 |
| FR-2 | [Description] | P1 |
## Non-Functional Requirements
- **Performance**: Response time < 200ms
- **Scalability**: Support 10K concurrent users
- **Availability**: 99.9% uptime
- **Security**: [Requirements]
## Technical Design
### Architecture
[Diagram or description]
### API DesignPOST /api/v1/resource Request: { "field": "value" } Response: { "id": "123", "field": "value" }
### Database Schema
```sql
CREATE TABLE resources (
id UUID PRIMARY KEY,
field VARCHAR(255)
);Implementation Plan
| Phase | Timeline | Deliverables |
|---|---|---|
| 1 | Week 1-2 | Core functionality |
| 2 | Week 3 | API endpoints |
| 3 | Week 4 | Testing & docs |
Testing Strategy
- Unit tests: 80% coverage
- Integration tests: API endpoints
- E2E tests: Critical flows
Risks & Mitigations
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| [Risk] | Medium | High | [Plan] |
Success Criteria
- All P0 requirements implemented
- Tests passing
- Performance targets met
- Documentation complete
## Full Template
See [references/template.md](references/template.md) for a comprehensive copy-paste template including:
- Complete metadata section
- Success metrics tables
- Architecture diagrams
- Detailed API design sections
- Security threat analysis
- Monitoring & observability
- Risk assessment matrix
- Rollout and rollback plans
- Dependencies tracking
- Open questions section
## Best Practices
**Do:**
- Include measurable acceptance criteria
- Add architecture diagrams
- Define explicit API contracts
- Quantify performance targets
- Document risks and mitigations
- Get stakeholder review before implementation
- Include security considerations
- Define rollback procedures
**Don't:**
- Use vague requirements ("fast", "scalable")
- Skip non-functional requirements
- Ignore security considerations
- Leave alternatives unexplored
- Omit testing strategy
- Forget dependencies and risks© secondsky, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/technical-specification/skills/technical-specification of secondsky/claude-skills.
- SKILL.md
- references/template.md
Open the folder on GitHubat commit 8837836
Compare with similar skills
Technical Specification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Technical Specification this skillsecondsky/claude-skills | 227 | — | ~754 | Automated safety check: Pass | MIT | |
| Architecture Guidelineseser/stack | 128 | — | ~516 | Automated safety check: Pass | Custom licence | |
| Schematicblader/schematic | 240 | — | ~2.2k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
More from secondsky/claude-skills
All 169 skills in this repoTanstack AI
secondsky/claude-skills
TanStack AI (alpha) provider-agnostic type-safe chat with streaming for OpenAI, Anthropic, Gemini, Ollama.
Auto Animate
secondsky/claude-skills
AutoAnimate (@formkit/auto-animate) zero-config animations for React.
Base UI React
secondsky/claude-skills
MUI Base UI unstyled React components with Floating UI. An agent skill from secondsky/claude-skills.
Cloudflare Images
secondsky/claude-skills
This skill should be used when the user asks to "upload images to Cloudflare", "implement direct creator upload", "configure image transformations", "optimize WebP/AVIF", "create image variants"…
Cloudflare Nextjs
secondsky/claude-skills
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare).
Cloudflare Sandbox
secondsky/claude-skills
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge.
Related
Categories
Questions about Technical Specification
What does Technical Specification do?
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Technical Specification is an agent skill from secondsky/claude-skills. Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies.
When should I use Technical Specification?
Technical Specification fits situations like: planning features; documenting system design; creating architecture decision records.
How do I install Technical Specification in Claude Code?
Run `npx skills add secondsky/claude-skills --skill technical-specification -a claude-code`. Or copy the skill folder (plugins/technical-specification/skills/technical-specification in secondsky/claude-skills) into .claude/skills/technical-specification in your project. Claude Code loads it when a task matches its description.
How do I install Technical Specification in Codex?
Run `npx skills add secondsky/claude-skills --skill technical-specification -a codex`. Or copy the skill folder (plugins/technical-specification/skills/technical-specification in secondsky/claude-skills) into .agents/skills/technical-specification in your project. Codex loads it when a task matches its description.
Can I use Technical Specification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add secondsky/claude-skills --skill technical-specification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technical-specification, .gemini/skills/technical-specification, .github/skills/technical-specification and .opencode/skills/technical-specification in your project.
What does Technical Specification need to run?
SKILL.md names no scripts, command-line tools or credentials: Technical Specification is instructions for the agent only.
Does Technical Specification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Technical Specification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Technical Specification use?
Technical Specification is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Technical Specification use?
About 754 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Technical Specification?
Skills that share tags, products or a category with Technical Specification: Architecture Guidelines (eser/stack, 128 stars), Schematic (blader/schematic, 240 stars), PR Design Doc (OpenHands/OpenHands, 90k stars) and Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Technical Specification?
secondsky (a GitHub user) maintains it in secondsky/claude-skills, which has 227 GitHub stars. The repository holds 169 skills in this directory. The repository was last updated on September 28, 2026.
Source: secondsky/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.