Skip to content
TrustedSkillsbeta
Back to all skills

Design Documentation

Checked
jasonkneen·vlatest·writing·MIT

Helps with design, documentation as part of writing, documentation, and content creation workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jasonkneen/kiro --skill design-documentation -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jasonkneen

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jasonkneen/kiro at 22577b636d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
22577b636d
Manifest
skills/design-documentation/SKILL.md
Scanned
1 file, 386 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in creating technical design documentation, bridging the gap between requirements and implementation. It guides users through documenting architecture decisions, component designs, and system interactions, providing a structured approach to planning technical work. The skill emphasizes understanding requirements, researching options, defining architecture, designing components, and outlining data models and testing strategies.

When to use it

  • After requirements are complete and approved.
  • When planning the technical implementation of a feature.
  • When multiple developers will be working on a single feature.
  • To document important architectural decisions.
  • For features involving complex integrations.

Key capabilities

  • Provides a standard template for design documents, including sections for Overview, Architecture, Components and Interfaces, Data Models, Error Handling, and Testing Strategy.
  • Guides users through a step-by-step process: Requirements Analysis, Research & Context Building, Defining System Architecture, Designing Components and Interfaces, and defining Data Models.
  • Includes guidance on analyzing requirements (functional, non-functional, constraints, integration points).
  • Facilitates research documentation with sections for Sources, Key Insights, and Impact on Design.
  • Supports documenting architecture diagrams using Mermaid syntax.

Example prompts

  • "Create a design document outline for the new user authentication feature."
  • "Help me define the architecture of the payment processing system."
  • "What are some key considerations when designing components for a microservice?"

Tips & gotchas

  • Ensure all functional and non-functional requirements are understood before beginning the design process.
  • The skill provides a template; adapt it to fit the specific needs of your project.
  • Consider security and compliance implications during both the research and design phases.