Docs & writing
16,621 rows, by stacks then stars
3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid
imtiazrayhan/agentscamp-library/skills/openapi-doc-writer Skill
1★ repoProduce and maintain OpenAPI documentation for an HTTP API. Use when documenting endpoints, request/response schemas, or generating API reference docs.
imtiazrayhan/agentscamp-library/skills/readme-generator Skill
1★ repoGenerate or refresh a project README grounded in the actual repository. Use when a project has no README, a stale one, or you want install/usage/scripts/structure sections that match the real code.
imtiazrayhan/agentscamp-library/skills/release-notes-writer Skill
1★ repoWrite user-facing release notes — the curated 'what's new and what it means for you' — by starting from the real changes (git log / merged PRs / the changelog since the last release) and translating developer-speak into user impact, grouped by what the user cares about with breaking changes and required actions surfaced first. Use when shipping a release to users or customers and the raw commit log isn't something a user should read, when you need a published GitHub-release / blog / in-app announcement, or when a breaking change must be made unmissable so upgrades don't break.
imtiazrayhan/agentscamp-library/skills/runbook-writer Skill
1★ repoWrite an operational runbook a half-asleep on-call engineer can execute at 3am — scoped to ONE alert, leading with how to confirm the problem, the copy-pasteable mitigation that stops user pain, then diagnosis, escalation, and verification. Use when an alert has no documented response, after an incident exposed a missing procedure, or when standing up on-call for a service.
imtiazrayhan/agentscamp-library/skills/version-bumper Skill
1★ repoBump the project version everywhere it lives in one consistent pass — package.json, lockfile, nested/CLI package manifests, version constants, README badges, docs — then roll the changelog's Unreleased section under the new version and stage an annotated git tag. Use when you've already decided the new version (X.Y.Z or a pre-release like -rc.1) and need every artifact updated to the same value without drift, or before cutting a release.
Jody09-dotcom/constructionx-skills/skills/site-diary Skill
1★ repoGenerate a daily UK construction site diary from a brief site-manager input. Use when the user asks for "site diary", "daily diary", "end of day report", "site log", or needs to write up a day's works. Captures weather, labour, plant, deliveries, works completed, delays, incidents, visitors, photos. UK construction conventions.
SkillMedev/social-media-studio/skills/hashtag-strategist Skill
1★ repoBuilds a tiered hashtag and keyword set sized to the account's actual reach - mixing broad, niche, and branded tags per platform limits and screening out banned, spammy, or shadow-flagged tags. Use when someone asks "what hashtags should I use", "build me a hashtag set for this post", "audit my tag block", or is creating reusable tag sets per content pillar on Instagram, TikTok, LinkedIn, X, or YouTube. Do NOT use for writing the caption itself - use social-caption-writer instead. Do NOT use for clustering SEO search keywords by topic or intent - use keyword-cluster-builder instead.
The same file is in 1 other repository
SkillMedev/social-media-studio/skills/linkedin-post-writer Skill
1★ repoWrite LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win into a LinkedIn post". Do NOT use for Twitter/X threads - use tweet-thread-builder instead. Do NOT use for scheduling across a monthly calendar - use social-content-calendar instead.
The same file is in 3 other repositories
SkillMedev/social-media-studio/skills/social-caption-writer Skill
1★ repoWrite one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a dedicated standalone LinkedIn post - use linkedin-post-writer instead; or a multi-post X thread - use tweet-thread-builder instead; or to adapt one existing piece of content into versions for several channels - use cross-platform-reformatter instead.
The same file is in 1 other repository
SkillMedev/social-media-studio/skills/tweet-thread-builder Skill
1★ repoTurn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use linkedin-post-writer instead. Do NOT use for adapting one finished piece across many platforms - use content-repurposing instead.
The same file is in 2 other repositories
stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/go-nogo-memo Skill
1★ repo[discovery-phase pack · deliverables] Produces a single GO / PIVOT / KILL memo consolidating all evidence into a one-page decision document. The only artifact most senior stakeholders read. Adapted for outsourcing — decision-owner is typically the client, agency provides recommendation with evidence chain.
SkillMedev/course-creator-launch-system/skills/lesson-plan-builder Skill
1★ repoBuilds a complete single-lesson plan - measurable objective, timed four-part arc (hook, direct instruction, guided practice, closure), a formative check with a proceed/re-teach rule, and differentiation notes - clear enough that a substitute could run it. Use when someone asks "write a lesson plan for...", "plan a 50-minute class on photosynthesis", "how should I structure tomorrow's lesson", or "turn this standard into a lesson". Do NOT use for sequencing a multi-week unit or full course - use curriculum-mapper instead; for deep per-learner adaptation of an existing lesson, use differentiated-instruction; for writing the quiz itself, use quiz-generator.
The same file is in 2 other repositories
SkillMedev/legacy-modernization/skills/tdd-expert Skill
1★ repoDrive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.
The same file is in 3 other repositories
Fusion-Data-Company/bristol-os/plugins/bristol-os/skills/deal-memo Skill
1★ repoAssemble research into a polished investment committee memo, market study, or deal one-pager. Use when the user says "write the memo," "put together an IC memo," "make a one-pager," "turn this into a document for the committee/lenders/LPs," or wants research packaged into a deliverable.
Fusion-Data-Company/bristol-os/plugins/bristol-os/skills/report-visuals Skill
1★ repoMake an infographic, slide, or chart for a report — Bristol-branded, zero setup. Use whenever a deliverable would land better with a visual (deal snapshot, market study, IC deck, one-pager header), or when the user says "make an infographic," "add a slide," "make it look good," "chart this." Proactively add a visual when it helps — don't wait to be asked.
HelloThisWorld/agent-skill-verification-template/skills/openmind-glossary Skill
1★ repoResolve a term against Open Mind's deterministic, source-traceable glossary — verbatim definitions with file:line provenance, exact-token lookup, honest "not found" for unknown terms. Runs Open Mind's real Python implementation through the skill bridge.
simanam/theaiteam/team/skills/docs/doc-coauthoring Skill
no license1★ repoGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
The same file is in 39 other repositories
simanam/theaiteam/team/skills/marketing/content/content-strategy Skill
no license1★ repoWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.
The same file is in 2 other repositories
simanam/theaiteam/team/skills/marketing/content/copywriting Skill
no license1★ repoWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
The same file is in 5 other repositories
simanam/theaiteam/team/skills/marketing/sales-revops/sales-enablement Skill
no license1★ repoWhen the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
The same file is in 2 other repositories
simanam/theaiteam/team/skills/meta/writing-skills Skill
no license1★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
The same file is in 7 other repositories
simanam/theaiteam/team/skills/product/writing-plans Skill
no license1★ repoUse when you have a spec or requirements for a multi-step task, before touching code
The same file is in 1 other repository
cabbagecachekid/neon-jetpack/skills/journey-map Skill
1★ repoUse when the user wants to create, map, or visualize a user journey, customer journey, experience map, or milestone map — "map the journey," "build a journey map," "chart the experience from X to Y," or any request to represent a user's progression through a product over time. Also use when converting research findings, interview synthesis, or funnel data into a journey visualization, and even when the user's draft framing is screen-based ("map our onboarding screens"). Works in FigJam when a write-capable Figma connection exists (e.g. the claude.ai Figma connector), and falls back to a portable markdown matrix when it doesn't.
cabbagecachekid/neon-jetpack/skills/line-edit Skill
1★ repoPolish a draft the author already wrote — fix grammar, punctuation, awkward phrasing, wordiness, and clarity at the sentence level WITHOUT changing meaning or flattening voice. A light-touch line editor, not a rewriter. Defaults to a professional register (business email). Use when the user says "polish this," "clean up this email," "line-edit," "proofread," "tighten this," "fix the grammar," "make this read better/more professional," or hands over a draft email/message/doc and wants it sharper. Do NOT use for tone, positioning, cockiness, or AI-tells work — that is full-review / cringe-check / ai-written-check.
iwritec0de/wp-dev/skills/verification Skill
1★ repoThis skill should be used before claiming any work is complete, before committing, before creating PRs, or before reporting task status. Enforces fresh verification evidence for all completion claims in WordPress/PHP projects. Provides the verification gate methodology: run commands, read output, then report.
iwritec0de/wp-dev/skills/wordpress-i18n Skill
1★ repoThis skill should be used when the user asks to "internationalize a plugin", "add translations", "set up i18n", "create a POT file", "translate strings", "load text domain", "use wp_set_script_translations", "add translator comments", or mentions "i18n", "l10n", "gettext", "text domain", "translation", "localization", "multilingual", "Poedit", "wp i18n make-pot", "wp_localize_script", "wp_set_script_translations", "__()".
iwritec0de/wp-dev/skills/wordpress-standards Skill
1★ repoThis skill should be used when the user asks to "follow WordPress coding standards", "name functions correctly", "organize plugin files", "write DocBlocks", "set up WPCS", "use Yoda conditions", or mentions "WordPress coding standards", "WPCS", "naming conventions", "file organization", "DocBlock", "text domain", "i18n", "autoloading", "plugin structure", "theme structure". Provides WordPress coding standards and conventions including naming, file organization, coding style, and documentation standards as defined by WPCS.
iwritec0de/wp-dev/skills/wp-hooks Skill
1★ repoThis skill should be used when the user asks to "document hooks", "generate a hooks reference", "list hooks", "show custom hooks", "generate hook docs", or mentions "hook documentation", "what hooks exist", "do_action", "apply_filters". Scans PHP source for do_action() and apply_filters() calls and produces detailed documentation with parameters, examples, and usage context.
SkillMedev/content-marketing-engine/skills/email-newsletter-pro Skill
1★ repoWrite recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or monthly", or "help me structure this issue". Do NOT use for automated onboarding or behavior-triggered sequences - use email-drip-builder instead. Do NOT use for inbox placement and spam-folder problems - use email-deliverability instead.
The same file is in 2 other repositories
SkillMedev/content-marketing-engine/skills/linkedin-post-writer Skill
1★ repoWrite LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win into a LinkedIn post". Do NOT use for Twitter/X threads - use tweet-thread-builder instead. Do NOT use for scheduling across a monthly calendar - use social-content-calendar instead.
The same file is in 3 other repositories
SkillMedev/content-marketing-engine/skills/tweet-thread-builder Skill
1★ repoTurn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use linkedin-post-writer instead. Do NOT use for adapting one finished piece across many platforms - use content-repurposing instead.
The same file is in 2 other repositories
SkillMedev/document-studio/skills/executive-summary Skill
1★ repoCompresses long reports, memos, and analyses into a decision-ready one-page summary (250-350 words) - bottom line up front, 3-5 evidence-backed key findings, a specific owned-and-dated recommendation, risks with mitigations, and the exact decision or resource being requested - plus a separate list of unverifiable claims to probe. Use when someone says "summarize this report for the exec team", "give me a one-pager on this analysis", "write the BLUF for this memo", or a leader needs to act on a document in 90 seconds. Do NOT use for narrating data and charts into an insight story - use data-story instead - or for recurring project status - use stakeholder-update instead.
The same file is in 1 other repository
SkillMedev/document-studio/skills/formatted-report-writer Skill
1★ repoProduces long-form business and consulting reports with a standalone executive summary, three-level heading hierarchy, and skimmability rules that let a busy reader navigate in under two minutes. Use when someone asks "write up this analysis as a report", "structure my strategy brief", "turn these findings into a client deliverable", or "make this document skimmable for executives". Do NOT use for presenting user-research findings to a product team - use research-readout instead; for a one-paragraph-to-one-page condensation of an existing document, use executive-summary; for slide-based delivery, use slide-deck-builder; for academic papers, use academic-essay.
The same file is in 1 other repository
SkillMedev/document-studio/skills/one-pager-designer Skill
1★ repoWrites a decision-driving one-pager - problem, evidence, impact, and a specific ask compressed into a single page readable in under three minutes. Use when someone asks "turn this into a one-pager", "write a brief for leadership", "I need a one-page pitch for this decision", or is preparing a document a busy reader must act on from one page. Do NOT use for a client-facing sales proposal with pricing and scope - use sales-proposal-writer instead; for condensing an existing long document use executive-summary; for multi-slide narratives use slide-deck-builder.
The same file is in 1 other repository
dayvisonassis/sdd-skills/skills/evaluator Skill
1★ repoExternally evaluates an already-implemented feature against its contract.md (environment, quality gates, coverage manifest, observable criteria), producing screenshots, a report, and chat findings. Owns the evaluation loop — keeps the attempt counter in progress.json, decides the state (CLEAN/FAIL/PENDING/ABORTED), and routes each failure: code failures (gate/observable) to fix-runner, test failures to the matching test-writer (then confirmed by the matching test-validator) before resuming. Loops until CLEAN, PENDING, or ABORTED.
dayvisonassis/sdd-skills/skills/gate-builder Skill
1★ repoBuilds the deterministic quality-gate infrastructure for a project (typecheck, lint with zero-warnings, dependency/architecture checks, tests, dead-code, and a single runGate entry point) from the Deep Analysis Report (+ Architecture Analysis Report). Auto-detects greenfield vs. brownfield, proposes a gate plan for confirmation, then writes the configs/scripts and verifies each gate runs. The gates it builds are later declared in each feature's contract.md by spec-writer.
dayvisonassis/sdd-skills/skills/implement-feature Skill
1★ repoImplements a feature autonomously based on its spec, plan, AND contract.md, committing one commit per phase, satisfying the contract's quality gates and observable criteria, writing progress.json, and reporting results against the feature's acceptance criteria. Delegates test writing to the matching test-writer skill (unit/integration/monorepo) by path/stack when the project fits, and falls back to writing tests itself otherwise.
dayvisonassis/sdd-skills/skills/integration-test-validator Skill
1★ repoAudits PABX backend integration tests (apps/backend/__tests__/integration/) against the integration-test-writer rules, producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected integration test conforms before resuming evaluation, or run directly by a user.
dayvisonassis/sdd-skills/skills/integration-test-writer Skill
1★ repoPlans and implements comprehensive integration tests for the PABX backend (apps/backend/__tests__/integration/) using Jest + supertest against a real test database. Runs interactively (3 phases with an approval checkpoint) when a user calls directly, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing integration test flagged by the evaluator. Enforces PABX rules (setupTestDatabase, try-finally cleanup, foreign-key order, English-only, NODE_ENV=testing, batches). Never modifies production code.
dayvisonassis/sdd-skills/skills/monorepo-unit-test-writer Skill
1★ repoPlans and implements unit tests for any PABX monorepo app EXCEPT apps/backend and apps/frontend — auto-detecting the stack (node-express, node-worker, or python-fastapi) and applying stack-specific patterns. Runs interactively (3 phases with an approval checkpoint) when a user calls directly, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing test flagged by the evaluator. Enforces PABX rules (mock-before-import, Promise.all() mocks, GPU/torch mocks, English-only, batches). Never modifies production code.
dayvisonassis/sdd-skills/skills/prd-writer Skill
1★ repoGenerate complete PRDs (Product Requirements Documents) through iterative clarification. Use when: (1) Starting a new project and need structured requirements, (2) Creating product specifications with 9-section PRD format, (3) Defining product scope from a description or context files. Keywords: "prd", "product requirements", "create PRD", "generate PRD", "new product", "requirements document".
dayvisonassis/sdd-skills/skills/spec-writer Skill
1★ repoGenerates technical implementation spec, plan, AND an operational contract for one or more features based on PRD, codebase analysis, and iterative clarification. Produces contract.md (environment contract, quality gates, coverage manifest, observable criteria) consumed by implement-feature and evaluator. Supports batch mode for generating multiple features from the same wave in parallel.
dayvisonassis/sdd-skills/skills/unit-test-validator Skill
1★ repoAudits unit tests in the PABX monorepo (Angular frontend .spec.ts + Node.js backend __tests__/unit/) against the unit-test-writer rules, producing a compliance report with a PASS/FAIL/PASS WITH WARNINGS verdict, per-violation severity, and fix suggestions. Read-only — never writes or fixes tests. Dispatched by the evaluator to confirm a corrected test conforms before resuming evaluation, or run directly by a user.
dayvisonassis/sdd-skills/skills/unit-test-writer Skill
1★ repoPlans and implements comprehensive unit tests for the PABX monorepo — Angular frontend (Jest + jest-preset-angular, .spec.ts) and Node.js backend (Jest, apps/backend/__tests__/unit/). Runs interactively (3 phases with an approval checkpoint) when called by a user, or autonomously (no pause) when dispatched by implement-feature/evaluator. Also runs in correction mode to fix a specific failing test flagged by the evaluator. Enforces PABX rules (real component imports, manual service instantiation, localStorage/jQuery mock order, Promise.all() mock correctness, cleanup, English-only). Never modifies production code.
iggmasterdev/badquality-lab/rca-prevention-facilitator/skills/rca-record-writer Skill
1★ repoEmits the finished RCA + Prevention Record as a .md file in a fixed template, and enforces the record's done-bar: systemic root cause, exactly one concrete prevention, a failure-class tag, and the "fix is not Done until root cause + prevention exist" rule. Use to write or finalize an RCA + Prevention Record, to check a record is complete before closing a SEV1/rollback ticket, or to format captured RCA findings into the shippable artifact. Called by rca-session-facilitator; usable standalone.
mehtab78/skills/skills/expert-technical-writer Skill
1★ repoTechnical writing specialist — READMEs, API docs, runbooks, changelogs, onboarding guides, release notes, summaries. Use for any task whose deliverable is prose about a technical system. Normally invoked by model-router.
pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/cross-platform-care Skill
no license1★ repoWrite scripts and file handling that survive the machine they didn't develop on — path separators, shell dialects, line endings, case-sensitivity, missing tools. Use when writing shell scripts, CI steps, path manipulation, file I/O, or install/setup instructions others will run.
pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/error-message-quality Skill
no license1★ repoWrite errors and log lines that name the failing thing, the offending value, and the likely fix — for the 3am reader. Use whenever writing a throw/raise, a log statement, a validation message, or a CLI/API error response.
Dolphinllc/claude-security-skills/skills/defensive/web/openapi-spec-security-scan Skill
1★ repoDefensive security scan for OpenAPI 3.x specifications (openapi.yaml / openapi.json). Detects missing global security, unprotected mutating operations, HTTP-only servers, loose schemas (additionalProperties true, missing required), wildcard CORS, missing 401/403 responses, PII in examples, and weakly-typed parameters. Invoke when the user asks to "review", "audit", or "scan" an OpenAPI / Swagger spec, or when editing files named openapi.{yaml,json}, swagger.{yaml,json}, or under api/ directories.
Dolphinllc/claude-security-skills/skills/offensive/web/nestjs-attack-probe Skill
1★ repoAuthorized self-pentest probe targeting NestJS-specific weaknesses. Tests global ValidationPipe gaps, missing @UseGuards on controller methods, default Swagger/OpenAPI exposure, WebSocket Gateway auth bypass, and TypeORM/Prisma raw query injection points discovered via OpenAPI. Use when the user asks to "pentest" their own NestJS app.
kasimmj/claude-skills-mega/skills/i18n-translate Skill
1★ repoExtract user-facing strings from source code into locale files, then translate them across locales. Supports JSON, YAML, .po, and Flutter .arb formats.
MehdiBatExpert/MarketingPilot/commands/mktg-copywriting Skill
1★ repoRédiger du copy persuasif B2B orienté conversion pour VibeCraft : landing pages, emails, posts X/LinkedIn, titres, CTAs, value propositions. Utiliser dès que Mehdi mentionne rédiger un texte de vente, améliorer un copy, écrire une landing page, un post LinkedIn/X, un titre accrocheur, un CTA, une value prop, une hero section, ou toute phrase du type "écris-moi", "améliore ce texte", "ça accroche pas", "rends ça plus percutant", "copy pour ma page", "texte pour mon produit". Applique les frameworks AIDA, PAS et Before/After/Bridge selon le canal. Toujours orienté bénéfice client, jamais feature-first. Ne pas utiliser pour : rédiger des emails outreach cold (utiliser fs-outreach), des séquences de relance (utiliser fs-sequence), ou des propositions commerciales (utiliser fs-offer).
kaustavr19/claude-skills/skills/ux-audit Skill
1★ repoPerform a thorough, professional UI/UX audit of any existing website or web product. Runs a CORE six-framework audit by default — Nielsen's 10 Heuristics, WCAG 2.2 Accessibility, Gestalt, UX Writing & Microcopy, Mobile/Responsive, and Performance & Core Web Vitals — and offers optional DEEP LENSES on request: Classic Usability Extended (Shneiderman, Gerhardt-Powals, Bastien & Scapin), Behavioural Laws (Hick's, Fitts's, Miller's, Jakob's, Peak-end), Trust & Persuasion (Fogg, Cialdini), and Interaction Design Principles (Norman, Tognazzini). Produces a markdown report with severity tiers, RAG status, fix recommendations, and effort estimates. Use whenever the user wants to audit, review, or critique a website, app, or web product's UI/UX — including "roast my site", "review this product", "what's wrong with this UI", "give me a UX review". Also trigger when the user shares a URL or screenshots for design feedback, or asks for a persuasion / behavioural-psychology / cognitive-load / dark-pattern review.
omarfarahatoglu-tur/ai-agent-skills/skills/engineering-team/api-documentation-engineer Skill
1★ repoOpen-source AI agent skills for Claude Code, OpenAI Codex, Cursor, and modern developer workflows.
steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/write-a-skill Skill
no license1★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
The same file is in 20 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/superpowers/skills/writing-plans Skill
no license1★ repoUse when you have a spec or requirements for a multi-step task, before touching code
The same file is in 12 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/superpowers/skills/writing-skills Skill
no license1★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
The same file is in 7 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/business-analytics/skills/data-storytelling Skill
no license1★ repoTransform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.
The same file is in 1 other repository
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/documentation-generation/skills/architecture-decision-records Skill
no license1★ repoWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
The same file is in 5 other repositories
steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/documentation-generation/skills/changelog-automation Skill
no license1★ repoAutomate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
The same file is in 1 other repository