Technical Writing
backnotprop/pstack/skills/technical-writingby backnotprop3a604672c46cd8187d2b19980eae0a34f9f91138No license1.3K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated yesterday
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Add to a SourceWeft workspace
- Open the skill in your dashboard and add it to a workspace.
- Enable it for the chats that should use it.
This skill is instructions only: it ships no scripts to execute.
Add to SourceWeftYou will be asked to sign in first, then taken straight to this skill.
Ask your agent to install it
Paste this prompt into Claude Code, Codex, Cursor or another agent that can run commands — or into SourceWeft chat. The agent reads this skill's install guide, shows you its source, license and scripts, and installs it with the SourceWeft CLI once you agree.
Read https://sourceweft.com/skills/gh-backnotprop-pstack-technical-writing-skills-technical-writing-1ac0292735d18485/install.md and install the skill it describes. Before installing, show me its source, license and whether it ships scripts, and wait for my OK. Ask me before changing anything else on my machine.Install it yourself from a terminal
For Claude Code, Codex, Cursor and other local agents. The SourceWeft CLI fetches the skill from its source repository at the commit scanned here, and verifies every file against the hashes recorded when the skill was scanned. If anything differs, nothing is written.
npx @sourceweft/cli skills install @backnotprop/technical-writingAdd --agent claude-code, codex, cursor or universal to choose which agent gets it (Claude Code by default).
Upstream installer — not verified by SourceWeft
The open-source skills installer fetches the same pinned commit, but does not check the files against the hashes SourceWeft recorded.
npx skills add https://github.com/backnotprop/pstack/tree/3a604672c46cd8187d2b19980eae0a34f9f91138/skills/technical-writingSource and attribution
Source:backnotprop/pstackinskills/technical-writingat commit3a60467
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from backnotprop/pstack
Unslop
backnotprop
Edits text to remove AI writing tells, following a numbered list of patterns to detect and fix.
Principle Type System Discipline
backnotprop
Guides agents to use static type systems to make illegal states unrepresentable and eliminate runtime failures.
Typescript Best Practices
backnotprop
TypeScript coding rules covering type modeling, narrowing, validation and testing discipline.
Principle Test Behavior Not Implementation
backnotprop
A guideline for writing tests that assert observable behavior with literal expected values instead of implementation details.
Tdd
backnotprop
Guides a test-driven bug fix: write a failing regression test first, then make the smallest fix and rerun it.
Teach
backnotprop
Explains a body of work plainly, combining how and why skills into one teaching explanation.
More in Writing & Content
Doc Coauthoring
anthropics
Guides users through a three-stage workflow to co-author documentation, proposals, specs and decision docs.
Writing Guidelines
vercel-labs
Reviews documentation and prose against fetched Writing Guidelines and reports style findings.
Job Post Builder
anthropics
Builds a hiring packet — job post, interview guide with rubrics, and offer letter template — from a role brief.
Write Spec
anthropics
Turns a feature idea or problem statement into a structured PRD with goals, user stories, requirements and metrics.
Draft Content
anthropics
Drafts marketing content such as blog posts, social posts, newsletters, landing pages, press releases and case studies.
Brand Voice Enforcement
anthropics
Applies existing brand voice guidelines to sales and marketing content, then explains the brand choices made.