ProstDev

@prostdev source repo

20 skills
0 followers
7 hours ago last updated

▌
Recap 2 · prostdev
Catch the user up when they open a session with no context loaded — reconstruct where things actually stand in the Claude app, claude.ai, or Cowork, then give a short, plain-language status report — the goal, where it stands, what's needed from them — plus a next-steps list split into mine/yours. Use when the user asks for a recap, says "catch me up" / "where did we leave off", or returns after being away. Read-only — never resumes or continues the work.

0
installs
▌
Add Skill · prostdev
Add a new skill to this marketplace repo the complete way — write an agnostic SKILL.md, place it in the right plugin, bump that plugin's version, and update the CHANGELOG and README. Use when adding a skill here, or turning an issue/idea into a shipped skill.

0
installs
▌
Recap · prostdev
Refresh anything stale from this session — a PR, a background agent, a running job — then give the user a short, plain-language status report — the session's goal, where things actually stand, and what's needed from them — plus a next-steps list split into mine/yours. Use when the user asks for a recap, says "catch me up" / "where did we leave off", or opens the session after being away with no context loaded. Read-only — never starts or continues work.

0
installs
▌
Commit · prostdev
Commit whatever is currently staged — commit only, no push. Use when the user says "commit", "commit this", "commit the staged changes". Does not stage anything and does not push. For committing AND pushing, use commit-and-push instead.

0
installs
▌
Save Session · prostdev
End-of-session routine. Saves learnings to .claude files following folder standards.

0
installs
▌
Create Pr · prostdev
Create PR

0
installs
▌
Writing Skills · prostdev
Writing Skills

0
installs
▌
Commit And Push · prostdev
Commit whatever is currently staged (if anything) and push. Use when the user says "commit and push", "ship it", or similar. Pushes even when there's nothing new to commit, so it also ships already-made local commits. Does not stage anything. For commit-only, use commit.

0
installs
▌
Add Faqs · prostdev
Add a FAQs section to the end of a ProstDev blog post for AEO. Use when the user wants to add or update frequently-asked questions / Q&A on a post (the "add FAQs", "FAQ section", "AEO Q&A" ask). Writes an optional `faqs` frontmatter array — answers GROUNDED in the post body, never fabricated — that renders a `## FAQs` section, mirrors into the `.md` endpoint, and emits FAQPage JSON-LD. Verifies with a build.

0
installs
▌
Close Session · prostdev
End-of-session wrap-up orchestrator. Runs accessibility-review, then verify-changes, fixing what each surfaces, then save-session. Use when the user wants to close out / wrap up a session cleanly in one step.

0
installs
▌
Verify Changes · prostdev
Post-change QA gate. After code has been changed — especially by a separate agent/fresh session — verify it type-checks and its tests pass (baseline- and matrix-aware), and that tests were actually added or modified to cover the new/changed behavior. Use before declaring a change done, or when reviewing another session's implementation.

0
installs
▌
Clarify Request · prostdev
Turn a vague or underspecified request into a clear, actionable brief by asking a few targeted questions before acting. Use when a prompt is ambiguous, the user isn't sure exactly what they want, or asks you to help clarify/refine what they're asking — across any domain (writing, design, legal, planning, research, defining a skill, a personal problem, etc.).

0
installs
▌
Tutorial Writing · prostdev
How to write step-by-step technical tutorials and setup/how-to guides a reader can follow top-to-bottom and succeed on the FIRST try — UI-fidelity, dependency-ordered steps, front-loaded values, scope/permission tables, "verify it worked" checkpoints, and the accuracy discipline that keeps commands from going stale. Use when writing or revising a hands-on numbered walkthrough, getting-started guide, or install/config how-to. For prose explainers see [[technical-content-structure]]; for SEO/frontmatter [[blog-seo-standards]].

0
installs
▌
Accessibility Review · prostdev bundle
Review, audit, or fix the accessibility of web UI — HTML, CSS, JS/JSX, or any component that renders a visible or interactive surface. Use when the user asks to check accessibility / a11y / WCAG / ARIA compliance, or mentions screen readers, keyboard navigation, color contrast, focus management, or making something usable for people with disabilities. Covers ~30 WCAG 2.2 Level A & AA success criteria with detection and remediation guidance.

0
installs
▌
Capture Learnings · prostdev
End-of-session review for the Claude app, Cowork, or any chat — decide what from this session is worth keeping, and route it to memory (durable facts/preferences) or a skill (repeatable workflows/domain knowledge). Writes the file directly when it can; otherwise hands the user paste-ready content and says where it goes. Use when wrapping up a session and asked to save, remember, or capture what was learned.

0
installs
▌
Blog SEO Standards · prostdev
SEO + AEO standards for writing or reviewing a technical blog post — title, meta description, headings, images, structured data, and the frontmatter that feeds them. Use when the user asks whether a post is "SEO-friendly", wants a title/description/heading/alt-text check, or is drafting an article to be found by search + AI answer engines. Separates EDITORIAL guidelines from the actual 2026 SEO numbers for word count, title length, and meta-description length. This is the SEO source of truth; for readability/structure see [[technical-content-structure]], for numbered walkthroughs [[tutorial-writing]].

0
installs
▌
How To Generate Secret · prostdev
Tell the user the command to generate a random 32-byte hex string for a secret, token, API key, or signing key. Use when the user needs to create a strong random secret.

0
installs
▌
Authoring App Skills · prostdev
Environment specifics for authoring skills that run in the Claude app, Cowork, cloud sessions, or the code-execution sandbox — bundled scripts, package dependencies, evals, and the account-sync loading model. Use when a skill targets the Claude desktop/web app or Cowork rather than a local Claude Code checkout. Assumes the craft in writing-skills.

0
installs
▌
Claude Md And Folder Standards · prostdev
Standards for editing any CLAUDE.md (each repo's root CLAUDE.md included — it lives outside .claude/ but these rules still govern it) and any file under .claude/ (skills, settings.json, hooks). Invoke before modifying any of them.

0
installs
▌
Technical Content Structure · prostdev
Readability + structure for long-form technical content — blog posts, concept explainers, and capability overviews people actually finish reading. Use when drafting or revising a prose article that feels dense, or for a scannability/voice/structure pass: reader-first framing, text chunking, the inverted pyramid, headline patterns, intro/conclusion anatomy, and calibrating content depth to the reader (runnable specifics for developers, trade-offs and rationale for architects). For SEO/frontmatter facts see [[blog-seo-standards]]; for numbered walkthroughs [[tutorial-writing]].

0
installs

20 published skills