Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

docs-writer-extended

Sterne2

Forks0

Aktualisiert4. April 2026 um 14:29

Token-efficiency extension for the docs-writer skill. This file MUST be read together with the parent docs-writer SKILL.md. Adds output rules to keep AI-agent-facing .md files lean.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

flaviosv

flaviosv/ai-coding-tooling

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	docs-writer-extended
extends	docs-writer
description	Token-efficiency extension for the docs-writer skill. This file MUST be read together with the parent docs-writer SKILL.md. Adds output rules to keep AI-agent-facing .md files lean.
metadata	{"version":"1.0.0","parent_skill":"docs-writer","source":"ai-coding-tooling (extended/)"}

docs-writer — Token Efficiency Extension

This file extends the docs-writer skill. The parent SKILL.md governs core documentation behavior. This extension adds output efficiency rules.

Output Rules

When generating or editing any .md file intended for AI agent consumption, follow Token Efficiency Rules.

Apply these rules to all generated content: reference files, SKILL.md files, docs/ files, and any other agent-facing documentation.

Mehr aus diesem Repository

gleiches Repository

mermaid-studio-extended

flaviosv/ai-coding-tooling

Extension for the mermaid-studio skill. This file MUST be read together with the parent mermaid-studio SKILL.md. The parent governs Mermaid diagram creation, validation, and rendering. This extension adds a required substitute renderer for multi-row C4 diagrams.

2026-07-072

code-review

flaviosv/ai-coding-tooling

Perform comprehensive code reviews on implementation code. Reviews local workspace changes by default, or a GitHub PR when a PR number is provided. Covers architecture, performance, code quality, API design, and security. Also performs full-codebase Performance Audits (P0–P3 findings report) when triggered by performance audit phrases. Technology agnostic — adapts to the project's stack using context files. Use when the user says "review my code", "code review", "check my code", "review my changes", "review this PR", or "review PR #123". Do NOT use for reviewing test files — use the tests-code-review skill for that.

2026-07-072

tlc-spec-driven-extended

flaviosv/ai-coding-tooling

Extension for the tlc-spec-driven skill. MUST be read together with the parent tlc-spec-driven SKILL.md. The parent governs spec-driven planning. This extension (1) declares how reference-level overlays load, (2) prioritizes planning before implementation for non-trivial work, (3) names feature artifacts `<TASK-ID>-<slug>`, (4) augments coding-principles with software-design/observability/stack-style references and routes security to the security-best-practices skill and UI work to web-design-guidelines, and (5) requires a persisted per-feature commit log (`commits.md`) of every atomic commit hash traceable to that feature.

2026-07-072

tests-code-review

flaviosv/ai-coding-tooling

Review test code quality, coverage patterns, and maintainability. Ensures tests are clear, independent, and provide meaningful coverage. Technology agnostic — adapts to the project's stack using context files. Use when the user says "review tests", "test code review", "check tests", "review test coverage", "review my tests", "review tests on PR #123", or "check tests PR #42". Do NOT use for writing new tests — use the tests skill for that. Do NOT use for reviewing implementation code — use the code-review skill.

2026-06-302

prompt-quality

flaviosv/ai-coding-tooling

Checks whether a task prompt follows the anatomy-of-a-prompt guidelines (9 layers: Task, Context Files, Reference, Success Brief, Rules, Conversation, Plan, Alignment, Push Intent). Auto-invoked before responding to any new task. Outputs a quality report — confirmed or missing layers — then proceeds without blocking. Never invoke for follow-ups, continuations, or responses to clarifying questions.

2026-06-302

architecture-evaluate

flaviosv/ai-coding-tooling

Creates, updates, and incrementally syncs the project context documentation that agents load at session start. Three modes. Full mode deep-scans the codebase (brownfield mapping) and writes nine context files to docs/codebase/ — PROJECT.md (overview, vision, goals), STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, CONCERNS.md, and PIPELINE.md. Incremental mode inspects the git workspace and syncs only what changed — inline API docs in source files, root context files (README.md, CLAUDE.md, AGENTS.md), and the context files in docs/codebase/ — and detects new packages. Package mode generates a scoped CLAUDE.md for an individual package/module. Use when the user says "evaluate architecture", "map codebase", "analyze existing code", "document current architecture", "update architecture docs", "refresh project context", "onboard project", "create project docs", "update project docs", "update docs", "document my changes", "sync documentation", "document recent changes", "evalua

2026-06-262

name	docs-writer-extended
extends	docs-writer
description	Token-efficiency extension for the docs-writer skill. This file MUST be read together with the parent docs-writer SKILL.md. Adds output rules to keep AI-agent-facing .md files lean.
metadata	{"version":"1.0.0","parent_skill":"docs-writer","source":"ai-coding-tooling (extended/)"}

docs-writer — Token Efficiency Extension

This file extends the docs-writer skill. The parent SKILL.md governs core documentation behavior. This extension adds output efficiency rules.

Output Rules

When generating or editing any .md file intended for AI agent consumption, follow Token Efficiency Rules.

Apply these rules to all generated content: reference files, SKILL.md files, docs/ files, and any other agent-facing documentation.