Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

pqforge-docs

Sterne2

Forks0

Aktualisiert14. Juni 2026 um 08:57

Maintain pqforge documentation from live code evidence. Use when editing README.md, CHANGELOG.md, CLAUDE.md, AGENTS.md, doc/**, wiki/**, the visibility manifest or generator, generated AI-discovery/editor files, or site/**. Also use when verifying API names, CLI commands, flags, performance numbers, package claims, links, or generated-document consistency.

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

turkananation

turkananation/pqforge

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	pqforge-docs
description	Maintain pqforge documentation from live code evidence. Use when editing README.md, CHANGELOG.md, CLAUDE.md, AGENTS.md, doc/, wiki/, the visibility manifest or generator, generated AI-discovery/editor files, or site/**. Also use when verifying API names, CLI commands, flags, performance numbers, package claims, links, or generated-document consistency.

pqforge Documentation

Follow the canonical repository documentation procedure in .claude/skills/pqforge-docs/SKILL.md. Read that file completely before making documentation changes; it is shared with Claude Code and contains the detailed claim boundary and manifest field map.

Workflow

Read pubspec.yaml, the latest CHANGELOG.md section, AGENTS.md, and the source/tests for every fact being documented.
Determine whether the target is hand-maintained or generated. Edit tool/visibility/visibility_manifest.json or its generator for generated visibility files.
Verify public symbols through lib/pqforge.dart or lib/pqforge_io.dart. Verify CLI commands and flags from bin/pqforge.dart and bin/src/.
Keep wording inside doc/security/CLAIM_BOUNDARY.md; do not upgrade pqcrypto algorithm evidence into module-validation claims.
Regenerate affected outputs.
Run:

dart run tool/agent/verify.dart docs

Run dart run tool/agent/verify.dart full when examples, public APIs, CLI behavior, or code-adjacent claims changed.

Mehr aus diesem Repository

gleiches Repository

pqforge-docs

turkananation/pqforge

Maintain pqforge documentation in lockstep with the code, with zero hallucinated APIs, commands, numbers, or links. Use whenever editing README.md, CHANGELOG.md, anything under doc/ or wiki/, the visibility manifest (tool/visibility/visibility_manifest.json), the generator, or any generated AI-discovery file (llms.txt, llms-full.txt, identity.json, faq-ai.txt, developer-ai.txt, ai.txt, robots*.txt, site/**, .github/copilot-instructions.md, .github/instructions/**, .cursor/rules/**, .windsurfrules). Enforces the verify-against-code protocol, the generated-vs-hand-maintained split, the claim boundary, the main-branch link rule, and the regenerate-and-validate checklist.

2026-06-142

pqforge-feature

turkananation/pqforge

Implement pqforge library, CLI, codec, recipe, streaming, hybrid, custody, test, or example features. Use for behavior changes under lib/**, bin/**, example/**, or test/** and for cross-cutting feature refactors.

2026-06-142

pqforge-release

turkananation/pqforge

Prepare and verify pqforge package releases. Use for version changes, changelog release notes, pub.dev archive checks, release branches, tags, GitHub binaries, or pub.dev publication.

2026-06-142

pqforge-feature

turkananation/pqforge

Implement pqforge features and fixes across the library, CLI, codecs, recipes, streaming, hybrid cryptography, key custody, tests, and examples. Use for any behavior change under lib/**, bin/**, example/**, or test/**, including new APIs, commands, flags, formats, cipher/provider behavior, performance changes, and cross-cutting refactors.

2026-06-142

pqforge-release

turkananation/pqforge

Prepare, verify, and audit pqforge releases. Use when changing the package version, updating release notes, preparing a release branch or tag, checking the pub.dev archive, validating generated version/visibility files, building release binaries, or publishing to pub.dev/GitHub.

2026-06-142

name	pqforge-docs
description	Maintain pqforge documentation from live code evidence. Use when editing README.md, CHANGELOG.md, CLAUDE.md, AGENTS.md, doc/, wiki/, the visibility manifest or generator, generated AI-discovery/editor files, or site/**. Also use when verifying API names, CLI commands, flags, performance numbers, package claims, links, or generated-document consistency.

pqforge Documentation

Workflow

Read pubspec.yaml, the latest CHANGELOG.md section, AGENTS.md, and the source/tests for every fact being documented.
Determine whether the target is hand-maintained or generated. Edit tool/visibility/visibility_manifest.json or its generator for generated visibility files.
Verify public symbols through lib/pqforge.dart or lib/pqforge_io.dart. Verify CLI commands and flags from bin/pqforge.dart and bin/src/.
Keep wording inside doc/security/CLAIM_BOUNDARY.md; do not upgrade pqcrypto algorithm evidence into module-validation claims.
Regenerate affected outputs.
Run:

dart run tool/agent/verify.dart docs

Run dart run tool/agent/verify.dart full when examples, public APIs, CLI behavior, or code-adjacent claims changed.