Docs & writing
16,633 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
aizech/clinical-skills/.cortex/skills/report-quality-review Skill
7★ repoMonitors and improves radiology report quality through systematic audit and feedback. Use when user mentions "report quality review", "discrepancy audit", "report completeness", "addendum analysis", or needs quality assurance.
aizech/clinical-skills/.cortex/skills/structured-reporting Skill
7★ repoCreate and optimize structured radiology reports using standardized templates. Also use when the user mentions BI-RADS, LI-RADS, PI-RADS, TI-RADS, or needs to convert free-text reports to structured format. For free-text analysis, see radiology-report-analysis.
aizech/clinical-skills/.qwen/skills/ai-report-assist Skill
7★ repoGuidance for AI-assisted structured reporting tools. Also use when the user mentions AI reporting, automated templating, speech-to-report, or wants to configure or optimize AI-assisted radiology reporting systems (RadAI, Abba, DeepRad).
aizech/clinical-skills/.qwen/skills/radiology-report-analysis Skill
7★ repoAnalyze structured/free-text radiology reports, extract key findings, measurements, and impressions. Also use when the user provides a report for review, summary, data extraction, critical findings identification, or report quality assessment. For structured reporting templates, see structured-reporting.
aizech/clinical-skills/.qwen/skills/report-quality-review Skill
7★ repoMonitors and improves radiology report quality through systematic audit and feedback. Use when user mentions "report quality review", "discrepancy audit", "report completeness", "addendum analysis", or needs quality assurance.
aizech/clinical-skills/.qwen/skills/structured-reporting Skill
7★ repoCreate and optimize structured radiology reports using standardized templates. Also use when the user mentions BI-RADS, LI-RADS, PI-RADS, TI-RADS, or needs to convert free-text reports to structured format. For free-text analysis, see radiology-report-analysis.
aizech/clinical-skills/.windsurf/skills/ai-report-assist Skill
7★ repoGuidance for AI-assisted structured reporting tools. Also use when the user mentions AI reporting, automated templating, speech-to-report, or wants to configure or optimize AI-assisted radiology reporting systems (RadAI, Abba, DeepRad).
aizech/clinical-skills/.windsurf/skills/radiology-report-analysis Skill
7★ repoAnalyze structured/free-text radiology reports, extract key findings, measurements, and impressions. Also use when the user provides a report for review, summary, data extraction, critical findings identification, or report quality assessment. For structured reporting templates, see structured-reporting.
aizech/clinical-skills/.windsurf/skills/report-quality-review Skill
7★ repoMonitors and improves radiology report quality through systematic audit and feedback. Use when user mentions "report quality review", "discrepancy audit", "report completeness", "addendum analysis", or needs quality assurance.
aizech/clinical-skills/.windsurf/skills/structured-reporting Skill
7★ repoCreate and optimize structured radiology reports using standardized templates. Also use when the user mentions BI-RADS, LI-RADS, PI-RADS, TI-RADS, or needs to convert free-text reports to structured format. For free-text analysis, see radiology-report-analysis.
aizech/clinical-skills/skills/ai-assistants/ai-report-assist Skill
7★ repoGuidance for AI-assisted structured reporting tools. Also use when the user mentions AI reporting, automated templating, speech-to-report, or wants to configure or optimize AI-assisted radiology reporting systems (RadAI, Abba, DeepRad).
aizech/clinical-skills/skills/analytics-quality/report-quality-review Skill
7★ repoMonitors and improves radiology report quality through systematic audit and feedback. Use when user mentions "report quality review", "discrepancy audit", "report completeness", "addendum analysis", or needs quality assurance.
aizech/clinical-skills/skills/clinical-documentation/radiology-report-analysis Skill
7★ repoAnalyze structured/free-text radiology reports, extract key findings, measurements, and impressions. Also use when the user provides a report for review, summary, data extraction, critical findings identification, or report quality assessment. For structured reporting templates, see structured-reporting.
aizech/clinical-skills/skills/clinical-documentation/structured-reporting Skill
7★ repoCreate and optimize structured radiology reports using standardized templates. Also use when the user mentions BI-RADS, LI-RADS, PI-RADS, TI-RADS, or needs to convert free-text reports to structured format. For free-text analysis, see radiology-report-analysis.
onatm/agent-skills/docs-feature-design Skill
7★ repoMaintain feature docs that explain user-visible behavior, goals, flows, and business rules without implementation detail. Use when feature scope, user workflows, or product behavior changes.
onatm/agent-skills/docs-product-requirements Skill
7★ repoCreate and maintain evidence-based Product Requirements Documents (PRDs). Use when writing, reviewing, or revising product requirements, initiative scope, success measures, or product decisions before technical design and delivery planning.
onatm/agent-skills/docs-product-roadmap Skill
7★ repoCreate and maintain outcome-driven product roadmaps. Use when defining, reviewing, or revising product priorities, strategic themes, Now/Next/Later horizons, roadmap phases, dependencies, or criteria for changing direction.
armelhbobdad/oh-my-skills/.claude/skills/bmad-cis-storytelling Skill
7★ repoCraft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"
armelhbobdad/oh-my-skills/.claude/skills/bmad-editorial-review-prose Skill
7★ repoClinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose
The same file is in 1 other repository
armelhbobdad/oh-my-skills/.claude/skills/bmad-index-docs Skill
7★ repoGenerates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder
The same file is in 1 other repository
armelhbobdad/oh-my-skills/.claude/skills/bmad-shard-doc Skill
7★ repoSplits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document
The same file is in 1 other repository
armelhbobdad/oh-my-skills/skills/oms-storybook-react-vite/10.3.5/oms-storybook-react-vite Skill
7★ repoAuthors Storybook v10 stories using the consolidated `storybook` package import surface for React plus Vite. Use when writing or editing `*.stories.tsx`, `preview.ts`, or `.storybook/main.ts` files on a Storybook 10.3+ project, including CSF3 story syntax, `play` functions with `storybook/test`, `preview-api` hooks, theming, MDX doc blocks from `@storybook/addon-docs/blocks`, and the a11y, themes, and vitest addons. Covers the `@storybook/react-vite` framework, `@storybook/react` renderer, and `@storybook/builder-vite` layer model so defects can be located at the right layer. Do NOT use for first-time project setup, framework selection, or upgrade migration (those flows are covered by the official upgrade CLI). Do NOT generate CSF2 default-export story arrays — v10 uses CSF3 named exports with the `satisfies` meta pattern, and training data frequently shows the wrong `@storybook/*` sub-package import paths that v10 consolidated into the single `storybook` package.
kambleakash0/agent-skills/skills/domain-glossary Skill
7★ repoExtract a DDD-style ubiquitous language glossary from the current conversation.
kambleakash0/agent-skills/skills/script-writer Skill
7★ repoScript-writer that drafts presentations, essays, emails, and slides using only the cognitive and persuasive heuristics from Patrick Winston's "How to Speak" lecture, rejecting conventional writing advice in favor of Winston's evidence-based rules.
kambleakash0/agent-skills/skills/spec-writer Skill
7★ repoCreate a comprehensive Product Requirements Document from conversation and repo context. Use when the user wants a PRD, product spec, feature requirements, or similar documentation.
seangeng/skills/remark-mermaid-tldraw Skill
7★ repoIntegrate the `remark-mermaid-tldraw` package so a project's ```mermaid code fences render as tldraw's warm, hand-drawn SVGs at build time (light + dark variants, zero client JS). Use this skill whenever the user wants their mermaid diagrams to look hand-drawn / sketched / less generic, mentions tldraw + mermaid together, wants build-time or pre-rendered diagrams in a blog or docs site, asks to "make my diagrams look better", or is wiring diagrams into MDX, Astro, Next.js, Eleventy, Vite, or React Router markdown. It encodes the exact install (including the headless-browser peer deps), the four wiring steps, the per-framework recipes, and — most importantly — the MDX-only `rehype-raw` gotcha that silently breaks the build if you miss it, plus how caching, light/dark, and the unsupported-diagram fallback work. Reach for it proactively when adding diagrams to any markdown/MDX pipeline; the default mermaid output is fine but flat, and this swaps it for the tldraw aesthetic without shipping any runtime JS.
seangeng/skills/write-like-a-human Skill
7★ repoStrip the AI tells out of generated prose so it reads like a person wrote it. Use this skill whenever you're asked to write or rewrite human-facing copy — a blog post, landing page, marketing email, newsletter, README intro, product announcement, social post, or any content a reader will actually read — and especially when the user says it sounds "robotic", "like AI", "too corporate", "soulless", or asks to "humanize", "make it sound natural", "less AI", or "punchier". Reach for it proactively before drafting any substantial piece of copy, not just when fixing existing text. It applies a voice (conversational, varied rhythm, real opinion) and a hard ban-list of buzzwords and filler that give machine writing away.
bh-rat/steer/skills/building-skills Skill
7★ repoBuilds an Agent Skill (SKILL.md) end to end with steer: design the trigger and components, scaffold with steer new, write the body, then gate on steer validate and a real run. Use when the user wants to create, write, or scaffold a skill, turn a document, API, or repeated workflow into a skill, or review, fix, or improve an existing skill. Also use when a skill needs credentials, persistent state, enforced steps, background processes, or learning wired in.
Harmeet10000/skills/skills/backend/C#_dotnet/csharp-docs Skill
7★ repoEnsure that C# types are documented with XML comments and follow best practices for documentation.
The same file is in 1 other repository
Harmeet10000/skills/skills/backend/C#_dotnet/run-tests Skill
7★ repoRuns .NET tests with dotnet test. Use when user says "run tests", "run my tests", "run these tests", "execute tests", "dotnet test", "test filter", "filter by category", "filter by class", "combine filters", "run only specific tests", "integration tests", "unit tests", "tests not running", "hang timeout", "blame-hang", "blame-crash", "crash dump", "TRX report", "TRX", "test report", "generate TRX", "TUnit", "treenode-filter", "target framework", "multi-TFM", or needs to detect the test platform (VSTest or Microsoft.Testing.Platform), identify the test framework, apply test filters, or troubleshoot test execution failures. Covers MSTest, xUnit, NUnit, and TUnit across both VSTest and MTP platforms. Also use for --filter-class, --filter-trait, --report-trx, --logger trx, --blame-hang-timeout, and other platform-specific filter and reporting syntax. DO NOT USE FOR: writing or generating test code, CI/CD pipeline configuration, or debugging failing test logic.
Harmeet10000/skills/skills/backend/FastAPI_Python/mojo-syntax Skill
7★ repoHelp to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
The same file is in 1 other repository
Harmeet10000/skills/skills/backend/Golang/golang-documentation Skill
7★ repoComprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
The same file is in 1 other repository
Harmeet10000/skills/skills/backend/mojo/mojo-syntax Skill
7★ repoHelp to write Mojo code using current syntax and conventions. Always use this skill when writing any Mojo code, including when other Mojo-specific skills (e.g., mojo-gpu-fundamentals) also apply. Use when writing Mojo code, translating projects to Mojo, or otherwise generating Mojo. Use this skill to overcome misconceptions with how Mojo is written.
Harmeet10000/skills/skills/backend/openapi-spec-generation Skill
7★ repoGenerate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
The same file is in 1 other repository
Harmeet10000/skills/skills/backend/rust-best-practices Skill
7★ repoGuide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
The same file is in 4 other repositories
Harmeet10000/skills/skills/writing-docs/doc-coauthoring Skill
7★ 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
Harmeet10000/skills/skills/writing-docs/documentation Skill
7★ repoCreates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
The same file is in 1 other repository
Harmeet10000/skills/skills/writing-docs/docx Skill
7★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
The same file is in 31 other repositories
Harmeet10000/skills/skills/writing-docs/press-release-writer Skill
7★ repoWrite professional press releases for any occasion, media type, and country. Use when the user wants to write, draft, or improve a press release, communiqué de presse, media announcement, news release, or PR statement — including product launches, funding rounds, partnerships, crisis communications, earnings, executive hires, events, M&A, open source milestones, and media advisories. Covers all release types, media targets (print, digital/wire, broadcast, social/SMPR, trade press), and region-specific conventions (Western/Eastern Europe, Americas, Middle East, Africa, Asia, Oceania). Also trigger when the user says 'I need to announce something' or 'how do I tell the press about X.'
The same file is in 1 other repository
Harmeet10000/skills/skills/writing-docs/substack-ghostwriting Skill
7★ repoWrite, optimize, and grow Substack content — both newsletter issues (email-first) and web posts (web-first articles/essays). Covers ghostwriting with voice matching, Substack algorithm optimization, Notes strategy, email formatting, SEO, growth tactics, and monetization planning. Use when the user mentions Substack, newsletters, write a newsletter issue, Substack post, Substack article, web post on Substack, evergreen content, SEO for Substack, newsletter growth, Notes strategy, ghostwrite for, match someone's voice, write in the style of, newsletter monetization, paid subscribers, or any task involving Substack as a platform. Also trigger for general article/newsletter writing even if Substack isn't named explicitly, or when the user wants to adapt existing content (blog post, talk, thread) into newsletter or web post format. Do NOT use for generic blog post writing without a newsletter/Substack context (-> See samber/cc-skills@technical-article-writer skill).
The same file is in 1 other repository
Harmeet10000/skills/skills/writing-docs/technical-article-writer Skill
7★ repoWrite compelling technical articles and blog posts for developer audiences. Use this skill whenever the user asks to write a blog post, technical article, or any long-form technical content. Also trigger when the user says 'write about [technical topic]', 'help me draft an article', 'turn this into a blog post', 'write a post about', 'I want to publish something about', or mentions writing for a developer audience. Covers the full pipeline: idea sharpening, hook/title generation, article structure, body drafting, and editing. Even if the user just says 'I want to write about X' without specifying format, use this skill. Do NOT use for platform-specific optimization, newsletter strategy, or ghostwriting voice matching.
The same file is in 1 other repository
estuary/agent-skills/skills/derivation-basics Skill
7★ repoFoundation for writing Estuary derivations — what they are, language choice (SQL/TypeScript/Python), project layout, flowctl workflow, stateless vs stateful shuffling, and universal gotchas. Read this before any other derivation-* skill. Use when user says "write a derivation", "how do derivations work", "create a derivation", "derivation setup", or before starting any transformation work.
estuary/agent-skills/skills/estuary-task-stats Skill
7★ repoCheck task processing statistics to see how much data and how many docs are moving. Use when checking throughput, diagnosing a stalled task, verifying data movement, or reporting on task activity. Use when user says "is data flowing", "how much data", "check throughput", "how many documents", "task not processing", "data not arriving", "stats", "bytes processed", "stalled capture", "no data in destination", "data volume", "task report", "usage report", or "how much data did we process".
bricerising/enterprise-software-playbook/skills/spec Skill
7★ repoWrite and maintain spec-first artifacts (service specs, API contracts via OpenAPI/protobuf/WebSocket schemas, ADRs, task lists, quickstarts). Use when creating specs/*.md, apps/*/spec/ bundles, or contracts/ docs, especially before major behavior changes or multi-agent collaboration. NOT for implementation task breakdown without spec artifacts (use plan); NOT for choosing system or code patterns (use architecture or design).
Agent-Engineer-Master/skill-engineer/marketing/analyzing-dtc-stores Skill
7★ repoUse when the user provides a DTC or ecommerce store URL and asks for a teardown, breakdown, brand analysis, competitor teardown, investor memo, store audit, deep dive, or 'what's going on with [brand]'. Produces an investor-grade markdown teardown report covering brand, market, unit economics, supply chain, channel mix, marketing, reviews, agentic-commerce readiness, risks, and a falsifiable verdict. Triggers: 'dtc teardown', 'brand teardown', 'store teardown', 'competitor teardown', 'analyze this store', 'investor memo on [brand]', 'break down [store url]'. Do NOT use for SEO-only audits, design-system extraction, lead-gen scraping, or general web scraping with no brand/investor focus.
Agent-Engineer-Master/skill-engineer/marketing/marketing-plan Skill
7★ repoDevelops a full go-to-market marketing plan for a new online business, product, or idea — covering beachhead market, ICP, competitive landscape, Dunford positioning with messaging, channel strategy with buyer journey mapping, budget allocation, pricing, content strategy with retention, 90-day launch timeline, PMF definition, first customer motion, and AARRR + GEV KPI framework with measurement setup. Produces a structured markdown plan saved locally. Activate when: "build a marketing plan", "create a GTM strategy", "how should I market my new product/brand/startup", "plan the launch for", "what channels should I use to launch", "write a marketing plan for". Do NOT activate for: auditing existing marketing performance, writing individual content pieces, running specific campaigns, or competitive analysis without a launch goal.
Agent-Engineer-Master/skill-engineer/operations/analysis-quality-review Skill
7★ repoReview-only multi-mode quality grader for reader-facing analytical deliverables (typically HTML reports with prose + charts/diagrams inline). Supports four modes: (1) `spec` returns a doc-type-specific authoring template the caller fills in; (2) `spec-judge` grades a filled-in authoring spec (storyline) BEFORE the caller writes the document — catches broken governing observation, MECE-overlap, Rumelt goal-not-strategy at the storyline stage and saves 60-70% of the iteration cost of post-hoc structure fixes; (3) `review pass: 1` audits argument STRUCTURE (Minto Pyramid, MECE, SCQA, Rumelt kernel, dot-dash storyline, issue-tree integrity) of the finished document; (4) `review pass: 2` audits READABILITY (action titles, so-what, specificity, code/jargon discipline, active voice, Frankenstein detection). Structure pass gates the readability pass. **Reviews reader-facing artifacts — HTML deliverables, executive reports, gate decisions — not machine artifacts or working markdown drafts.** The rule of thumb: if a human is expected to read it, it goes through this review (typically as HTML at standard+ strictness). If it's audit substrate, working scaffolding, or machine-readable data, it does NOT. The skill returns structured violation reports + a path to fix-patterns.md; the CALLING skill applies fixes using its own context. Invoke from any upstream skill that produces analytical reports, strategy decks, industry analyses, decision documents, or executive HTML. Recommended end-to-end caller flow at standard+ strictness: spec → spec-judge loop → write → render-to-HTML → review pass: 1 loop → review pass: 2 loop. Use phrases like 'run analysis-quality-review on X', 'get an authoring spec for a brief', or 'judge this storyline'. Do NOT invoke for: SEO/GEO content review (use seo-review-loop), code review, fact-checking, machine artifacts (YAML, JSON), working markdown drafts in audit folders, or short chat replies under ~200 words. Configurable strictness (low/standard/high) and document type (brief/deck/memo/decision-record/wiki/daily-note).
Agent-Engineer-Master/skill-engineer/operations/prompt-engineer-master Skill
7★ repoCreates robust long-form task prompts and agent briefs using production prompt engineering patterns (layered XML architecture, trust boundaries, anti-rationalization rules, numeric anchors). Invoke when the user needs to create an agent system prompt, write a complex task prompt, design a multi-agent workflow prompt, or produce prompts that are clearer, more reliable, and easier to debug. Does NOT activate for: short single-turn prompts, simple rewrites, asking Claude to explain prompt engineering concepts, or editing existing prose that is not a prompt.
Agent-Engineer-Master/skill-engineer/operations/write-report Skill
7★ repoReview-only quality grader for reader-facing analytical deliverables (HTML reports, executive briefs, strategy decks, decision documents). Modes: spec (returns authoring template), spec-judge (grades the storyline before writing), review pass 1 (argument structure), review pass 2 (readability), review pass 3 (humanization — verifies the caller's humanize edit landed: zero em-dashes, no AI tells, human texture); each pass gates the next. Returns structured violation reports; the CALLING skill applies fixes. Rule of thumb: if a human will read it, it goes through this review; machine artifacts, agent-read repo docs, and working drafts do not. Invoke via 'run write-report on X', 'get an authoring spec', or 'judge this storyline'. Do NOT use for SEO review (use seo-review-loop), code review, fact-checking, or short chat replies. Full mode/strictness/doc-type details in the skill body.
aka-kika/akakika-skills/skills/content/blog-post-publishing Skill
7★ repoUse when the user asks to create, add, convert, publish, or deploy a blog post from a draft, notes, Markdown, outline, or topic. Turns a draft into a complete, SEO/GEO-optimized post wired into the site (template, blog index, sitemap, routing) with QA and deploy. Framework-agnostic — discover the project's own conventions first.
aka-kika/akakika-skills/skills/maintenance/docs-update Skill
7★ repoUse when the user needs to update, improve, audit, or maintain documentation in a project. Covers READMEs, changelogs, API docs, inline comments, missing docs, and overall documentation quality. Works well before releases or when documentation has fallen behind the code.
HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/archetypes-storytelling-arcs Skill
no license7★ repoUse this skill when designing narrative content — landing pages, case studies, onboarding flows, marketing campaigns, sales decks, ad arcs. Trigger when picking how to frame a customer story, when writing a launch campaign, or when the user mentions "this campaign feels flat" or "we need a better narrative." Sub-aspect of `archetypes`; read that first.
HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-line-length Skill
no license7★ repoSet line length (measure) for prose — capping the maximum width of body text so lines stay in the 45–75 character range that supports comfortable sustained reading. Use when designing article layouts, documentation, email templates, dashboard copy, or any container that holds paragraphs of prose. Line length is the most fundamental readability decision because it directly affects the reader's eye movement; lines that are too long or too short both cost reading comfort.
HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability-rhythm-and-prose Skill
no license7★ repoApply paragraph rhythm and prose-level readability — calibrating leading, paragraph spacing, subheading frequency, and visual breathing room so that long-form text reads smoothly without fatigue. Use when designing article layouts, documentation, reports, transcripts, or any context with sustained prose. Beyond line length and legibility, the rhythm of prose layout — the rest points provided by paragraph breaks, the hierarchy provided by subheadings, the breathing room provided by margins — determines whether readers stay engaged with long content.
HDeibler/universal-design-principles/plugins/perception-and-hierarchy-principles/skills/readability Skill
no license7★ repoApply the principle of Readability — the ease with which sustained prose can be read, determined by line length, line height, paragraph rhythm, font choice for prose, and visual breathing room. Use when designing long-form content (articles, documentation, books, transcripts), writing email or report layouts, evaluating whether users can comfortably read paragraphs of text. Distinct from legibility (per-character clarity); readability is about the experience of reading sustained prose without fatigue. The two principles compose: readability requires legibility and adds prose-specific constraints.
Poorgramer-Zack/dart-expert-skills/skills/flutter-drift Skill
7★ repoImplements type-safe reactive SQL persistence in Flutter using Drift v2.32 (formerly Moor) built on SQLite with automatic code generation. Activates when defining table schemas with Drift DSL, writing type-safe join or subquery operations, handling schema migrations with MigrationStrategy, using reactive watch() streams for live UI updates, implementing ACID transactions, defining foreign key constraints or cascade deletes, enabling WAL mode for write performance, troubleshooting generated .g.dart type mismatches, migrating from sqflite or sqlite3 v2 to v3, using DAOs for query separation, or building offline-first apps requiring strong relational data integrity and compile-time SQL verification.
Poorgramer-Zack/dart-expert-skills/skills/openapi-to-dart Skill
7★ repoReads an OpenAPI 3.0 specification and manually implements a type-safe Dart API layer using Dio for HTTP, Freezed or Equatable for models, and json_serializable for serialisation. Use when given an OpenAPI/Swagger file (JSON or YAML) and asked to implement the API in Flutter/Dart, create Dart models from an API schema, build a Dio API client, implement endpoints from a spec, convert openapi to dart, or set up a data/network layer from an API contract. Handles $ref resolution, oneOf union types, enums, query params, request bodies, and DioException error mapping.
The same file is in 1 other repository
black-yt/skills/frontend-markdown-rendering Skill
no license7★ repo当需要在前端把最终 assistant 文本渲染为 Markdown,同时保留工具过程为纯文本/JSON,并支持表格、代码块、图片、KaTeX 公式、Mermaid 图和 workspace 本地图片安全访问时使用。
black-yt/skills/github-readme-writing Skill
no license7★ repo当需要为 GitHub 项目创建、重构或审阅高质量 README.md 时使用;参考 ResearchClawBench 风格,覆盖居中标题、徽章、导航、teaser、highlights、news、Mermaid、GitHub 公式渲染、quick start、citation 和 star history。
black-yt/skills/markdown-to-docx Skill
no license7★ repoUse when converting Markdown documents into Microsoft Word .docx deliverables, including articles, reports, announcements, release notes, project documentation, image-rich explainers, meeting materials, and public-facing drafts that need embedded local images, captions, readable headings, Chinese/English typography, visible word counts, and a deterministic Python conversion workflow.