Skip to content

Improve fingerprint authoring guidance - #301

Draft
awinther1 wants to merge 6 commits into
mainfrom
awinther/authoring-skill-clarity
Draft

awinther1 wants to merge 6 commits into
mainfrom
awinther/authoring-skill-clarity

Conversation

@awinther1

@awinther1 awinther1 commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Why

The bundled authoring skill needed clearer rules for turning supplied brand material into confirmed guidance. It also needed a stricter editing pass so node prose stays direct, specific, and free of repeated or vague language.

What

This PR strengthens the public authoring workflow and node-writing guidance.

How

The authoring recipe now starts from loose supplied material, separates observations from confirmed decisions, compares outside guidance against existing nodes, chooses the smallest useful form, and treats each edit as a complete package change.

The node recipe now adds sentence-level deduplication, plain-language editing, and concrete replacements for vague design jargon.

Risk

Low. This changes installed Markdown guidance only. It does not change the CLI, schema, package shape, or runtime behavior.

Testing

pnpm check:terminology passed.

pnpm exec vitest run packages/ghost/test/skill-bundle.test.ts passed in the original checkout. A clean worktree install was blocked by npm registry checksum errors, so its full pre-commit checks could not resolve yaml and cac.

Generated with Goose

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant