Technical Writing

Write and maintain CSS using consistent methodology, design systems, framework utilities, and minimal custom styles for better performance and maintainability. Use this skill when writing or modifying CSS files, style modules, Tailwind classes, styled-components, CSS-in-JS, or any styling code for UI components. Use this when applying utility classes, maintaining design tokens for colors/spacing/typography, working with CSS frameworks like Tailwind or Bootstrap, avoiding framework style overrides, optimizing CSS for production with purging/tree-shaking, or implementing responsive styling. Use this when working on .css, .scss, .module.css files or when adding className/style attributes to components.

Comprehensive guide for writing Playwright E2E tests in the Aldoa codebase. Use when creating new test files, debugging failing tests, or refactoring existing tests. Covers authentication patterns, helper functions, Semantic UI/React Select interactions, data generation strategies, and common testing scenarios.

Automated task lifecycle orchestrator for docs/tasks/ directory - identifies next ready tasks by priority, loads full context from markdown files, guides TDD implementation with Wallaby MCP, runs quality checks, and tracks completion. Use when user says "start next task", "what should I work on", "show ready tasks", or mentions specific task IDs like "start T0001".

Comprehensive guide for writing technical books in Markdown format. Use this skill when creating new chapters, managing code examples, reviewing content for technical accuracy and consistency, or organizing book structure (TOC, cross-references). Provides templates, validation scripts, and best practices for technical writing workflows.

Transforms markdown files into brand-compliant BAC HTML presentations with professional styling, proper typography, and integrated branding. Supports manual browser-based PDF export.

Unity/ゲームクライアントの画面機能ドキュメントを作成。指定された画面のPresenter、ViewModel、UseCaseなどのコードを調査し、プランナー視点でのゲーム体験に焦点を当てた非技術ドキュメントをMarkdown形式で生成します。glow-clientプロジェクト、Unity画面、プランナー向けドキュメント、画面仕様書作成で使用。

Use when writing any code - enforces clean architecture with descriptive names, real implementations, no backward compatibility concerns, and no lint suppressions

Push a local skill to the Notion skills database. Load when user mentions "share skill", "export skill", "push to notion", "add skill to database", or after creating a new skill with create-skill.

This skill should be used when converting technical blog posts (markdown files) into engaging LinkedIn posts that drive traffic and engagement. Use when the user provides a blog post file path or asks to create a LinkedIn post from their blog content.

Export Claude skills. Use to generate documentation of all available Claude Skills.

Skills providing all documentation related to Google ADK (App Development Kit).

Verify external libraries, APIs, and frameworks against current documentation before writing code. Use when about to implement features using external dependencies, when writing import statements for third-party libraries, when unsure if a pattern or method is current, or when the user mentions grounding or verification.

Templates and guidelines for writing internal communications including status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, and project updates. Use when drafting any form of internal team or company communication.

Update or create API documentation after making changes to the public interface of an API. Use when modifying existing endpoints, introducing new endpoints, or when API implementation changes are complete and tested.

Reference and maintain the project's technical stack documentation including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across all development work. Use this skill when choosing technologies for new features, when documenting technology decisions, when working with framework-specific code patterns, or when ensuring consistency with existing technology choices. Use this skill when working with any code file to verify it follows the conventions of the project's chosen frameworks and tools. Use this skill when setting up new dependencies, configuring build tools, or making architectural decisions about which libraries or services to use. Use this skill when onboarding new team members or creating technical documentation about the project's architecture and technology choices.

Use when you have a spec or requirements for a multi-step task, before touching code

Initialize .claude/ structure and surgically add PopKit section to CLAUDE.md without overwriting. Detects conflicts, creates config, prompts for Power Mode. Use for new projects only - use analyze-project for existing.

Use when implementing features or fixes in projects with tdd-guard installed. This skill guides the RED-GREEN-REFACTOR cycle with proper test registration, preventing common TDD violations like writing code before tests or implementing multiple tests simultaneously. Invoke when tdd-guard blocks an edit or when starting TDD work.

Best practices for writing effective Task tool prompts that produce clear, structured outputs from sub-agents. Covers context engineering, instruction clarity, output format specification, and parallel delegation patterns. MUST BE USED PROACTIVELY when spawning sub-agents to ensure high-quality results.

Enforce homelab-proxmox workflow patterns including single source of truth documentation, prompt logging, git commits, environment variables, and phase tracking. Use this skill when completing tasks, updating docs/ or CLAUDE.md files, or when workflow compliance validation is needed. Provides AI-powered fixes for violations.