Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "documentation-and-adrs" from https://skillstore.io/skills/addyosmani-documentation-and-adrs.md and its manifest at https://skillstore.io/api/skills/addyosmani-documentation-and-adrs/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
„documentation-and-adrs“ wird verwendet. We chose PostgreSQL over SQLite and MongoDB for a multi-user task application.
Erwartetes Ergebnis:
An ADR outline with status, context, relational data requirements, alternatives considered, the PostgreSQL decision, and operational consequences.
„documentation-and-adrs“ wird verwendet. Document a task creation endpoint that requires a title and returns an identifier.
Erwartetes Ergebnis:
API reference guidance covering the request fields, validation errors, authentication expectations, response details, and a short usage example.
„documentation-and-adrs“ wird verwendet. Create onboarding documentation for a project with a development server and test suite.
Erwartetes Ergebnis:
All 28 external-command detections are Markdown examples or inline command references in SKILL.md, not executable behavior. The environment-file and system-reconnaissance detections also point to documentation examples, and no prompt injection or data-exfiltration intent was found.
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-documentation-and-adrs?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-documentation-and-adrs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-documentation-and-adrs/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-documentation-and-adrs.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). documentation-and-adrs security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2@techreport{addyosmani-addyosmani-documentation-and-adrs-2026,
author = {addyosmani},
title = {documentation-and-adrs security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "documentation-and-adrs security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-documentation-and-adrs/audits/2"
identifiers:
- type: other
value: "skillstore:addyosmani-documentation-and-adrs:audit:2"
description: "Skillstore immutable audit report identifier"
Create an ADR that compares options, explains trade-offs, records the selected approach, and preserves consequences for future maintainers.
Draft consistent API documentation covering inputs, outputs, errors, authentication expectations, and representative usage guidance.
Build a practical README, changelog structure, and agent guidance so contributors can understand setup, architecture, conventions, and recent changes.
Create a concise ADR for this decision: [decision]. Include context, selected approach, two alternatives, consequences, status, and date. Use clear headings.
Review the repository context I provide and identify its ADR location, file format, numbering pattern, and headings. Then draft an ADR for [decision] that follows those conventions.
Write documentation for this public API: [API details]. Cover parameters, return values, validation, authentication, errors, and one realistic example. State unknowns instead of inventing behavior.
Design a documentation update for [project]. Propose ADRs for durable decisions, README sections for onboarding, API reference coverage, changelog entries, agent guidance, and a verification checklist. Preserve existing conventions and identify missing evidence.
Autor
addyosmaniLizenz
MIT
Skillstore-Revision
r2
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
5d5054f8a23586f9b500fece1cb613a9dffc787b
Aktualität der Wartung
19.9.2026
Nutzung
2 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md
Code anhand von fünf Qualitätsdimensionen überprüfen
Codeänderungen können Probleme hinsichtlich Korrektheit, Sicherheit, Architektur, Lesbarkeit und Performance verbergen. Dieser Skill wendet einen strukturierten Review-Prozess an und liefert priorisiertes, umsetzbares Feedback.
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Debug Errors with a Root-Cause Workflow
Debugging failures by guesswork wastes time and can hide the real cause. This skill provides a repeatable process for reproducing, isolating, fixing, and verifying problems.
Structure Better Context for Coding Agents
Coding agents lose accuracy when context is incomplete, stale, or excessive. This skill provides practical structures for focused sessions, durable rules, and reliable handoffs.
Professionelle Markdown-Dokumentation erstellen
von AutumnsGrove
Teams benötigen klare Projektdokumentation, die über README-Dateien, Changelogs und Beitragsleitfäden hinweg konsistent bleibt. Markdown Pro bietet Vorlagen, Struktur und unterstützende Workflows für ausgereifte technische Dokumentation.
Write Clear Go Documentation
von samber
Go projects often have incomplete comments, examples, and contributor guidance that slow adoption and maintenance. This skill provides structured guidance for writing, reviewing, and organizing documentation that matches Go conventions.
Zweisprachige GitHub-Release-READMEs generieren
von ZhanlinCui
Release-Dokumentation ist zeitaufwendig, wenn Teams englische und chinesische READMEs benötigen. Diese Skill generiert strukturierte zweisprachige READMEs aus Repository-Metadaten und geführter Konfiguration.
Repository-Architektur dokumentieren
von AstraBit-CPT
Repository-Dokumentation veraltet häufig, wenn sich Abhängigkeiten, APIs und Einrichtungsschritte ändern. Diese Fähigkeit analysiert Struktur und Integrationen und hilft anschließend dabei, README-, API-, Architektur-, Beitrags- und Integrationsdokumentation zu erstellen.
Großartige Repository-Scaffolds erstellen
von zjsxply
Das Erstellen einer ausgereiften Awesome-Liste erfordert eine sorgfältige Struktur, Beitragsregeln und Verifizierungsschritte. Diese Skill generiert aus einem Thema und Startressourcen ein fokussiertes Repository-Scaffold.
Klare technische Dokumentation erstellen
von shubhamsaboo
Teams haben oft Schwierigkeiten, technische Details in klare Dokumentation zu überführen. Dieser Skill strukturiert READMEs, API-Referenzen, Tutorials und Leitfäden für Claude, Codex und Claude Code.