Results for “technical-correctness”

Technical writing proficiency covering clarity principles, audience analysis, information structure, editing techniques, and style enforcement. Use when writing or improving any technical content — docs, specs, guides, or explanations. Also trigger for 'technical writing', 'write clearly', 'simplify this', 'rewrite for clarity', 'plain language', 'writing style', or 'editing pass'.

Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.

Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.

Enforces output quality, intellectual honesty, and continuous improvement across security analysis agents with anti-rationalization guards, self-critique loops, retry protocols, and quality gates.

Align a technical document with the actual code implementation and correct drift. Use when a user asks to update docs to match current behavior, audit a technical document against the repository, or fix stale architecture, API, workflow, or operator documentation.

Build and review high-quality technical documentation, including agent instruction files and contributor-governance files, with support for audits, multilingual parity, and sub-agent orchestration.

Use this skill for crawlability, indexability, metadata, canonical tags, robots, sitemaps, internal signals. Trigger when the task involves seo work related to Technical SEO Audit, production implementation, audits, debugging, strategy, or validation.

Use when writing Textual TUI CSS styles or checking valid CSS properties

Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.

Audits typographic decisions on a screen for scale usage, readability, consistency, and token compliance, providing specific fixes.

Audits technical SEO across nine categories including crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow, producing a scored report with prioritized fixes.

Deep technical SEO auditing covering crawlability, indexation, Core Web Vitals, site architecture, canonicalization, structured data validation, and performance optimization. Use when the user asks about technical SEO, site audits, crawl issues, indexation problems, Core Web Vitals, page speed, or site architecture optimization. For content-focused SEO, see the seo-content-writer skill.

Technical SEO, structured data, sitemaps, and meta tags.

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Identify error-prone APIs and dangerous configurations

A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Analyze weekly price charts for stocks, indices, crypto, or forex to identify trends, support/resistance, and probabilistic scenarios based purely on chart data.

Reviews and repairs risky or unclear code with minimal validated changes, running a fixed-point loop until the diff is clean across two consecutive review cycles.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.

Verify the article’s factual, product, citation, and link integrity before visual production.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

SSOT（Single Source of Truth）と実際のファイル/設定の整合性をチェックし、乖離があれば修正するスキル。 「SSOTチェックして」「SSOT整合性チェックして」「SSOT整理して」「SSOTのズレを直して」 「00_SYSTEM更新して」「乖離を修正して」と言った時にトリガーする。 /ssot-check でも呼び出せる。

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Verify TPM measured boot integrity and remote attestation using tpm2-tools, including PCR reading, event log replay, quote generation and verification, and golden baseline comparison.

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Write product-facing technical specs that clarify decisions, constraints, dependencies, and rollout.

Expert technical documentation specialist for developer docs, API references, and runbooks. Activate on: documentation, docs, README, API reference, technical writing, user guide, runbook, ADR, changelog, release notes, tutorial, how-to guide. NOT for: marketing copy (use copywriting skills), blog posts (use content skills), code comments (handled by developers).

Internal technical readiness drill assistant for release and handoff.

Tightens existing copy for clarity, accuracy, tone consistency, and executive readability without altering the underlying message.

Diagnose failures from runtime evidence before editing code.

Build and review high-quality technical docs as well as agent instruction files in your repository.