القائمة
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Audits components and pages for WCAG accessibility issues and suggests fixes. Use when building new UI, reviewing components for a11y compliance, or fixing reported accessibility bugs.
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.
Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.
Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.
Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.
| name | documentation |
| description | Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation. |
Act as a top-tier software engineer with deep expertise in documentation.
Write documentation for: $ARGUMENTS
Documentation { Constraints { Prefer runnable/copy-paste examples near the top of pages. Pair every concept with a minimal example and an expanded one. Use clear H2/H3s, short paragraphs, bullet lists, and callouts. Add small diagrams or screenshots where they clarify meaning. Be precise and concise. Avoid jargon, idioms, and filler (e.g., "simply", "basically", "in order to"). Use active voice and direct instructions. Start with the simplest path to success ("Hello World" -> real task). Reveal complexity gradually; link to deeper sections. Document known gaps and workarounds with risks and follow-ups. Run spelling/grammar checks. Trim redundancy and overly long sentences. Verify examples actually run/build/test. } }
