技術寫作
5624 skills in 文件 > 技術寫作
blog-to-linkedin
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.
skill-export
Export Claude skills. Use to generate documentation of all available Claude Skills.
google-adk
Skills providing all documentation related to Google ADK (App Development Kit).
external-docs
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.
internal-comms
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.
api-docs-writing
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.
global-tech-stack
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.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
project-init
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.
tdd-guard-workflow
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.
agent-prompting-delegation
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.
homelab-workflow
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.
solidity
Solidity smart contract development with Foundry. Covers writing, testing, security, deployment, and upgrades. Triggers on .sol files, contract, pragma solidity, forge.
react-testing
Testing patterns for React with Jest and React Testing Library. Use when writing tests, mocking modules, testing Zustand stores, or debugging test failures in React web applications.
portfolio-code-review
Code review for Paweł Lipowczan portfolio project (React+Vite+Tailwind SPA). Use when user wants to review code changes, pull requests, commits, or modifications in portfolio project. Verifies architecture compliance, SEO standards, accessibility (WCAG 2.1 AA), performance (Core Web Vitals), blog system (markdown frontmatter, OG images), prerendering setup, and edge cases. References docs/{PRD.md,SRS.md,TODO.md,blog/BLOG_WORKFLOW.md}. Focuses on bugs, edge cases, and conditions causing errors after deployment.
design-system-starter
Use this skill when creating or evolving design systems for applications. Provides design token structures, component architecture patterns, documentation templates, and accessibility guidelines. Ensures consistent, scalable, and accessible UI design across products.
gtm-javascript
Generate ES5-compliant JavaScript for Google Tag Manager Custom HTML tags. Use when writing GTM tags, dataLayer code, or analytics implementations.
notion-uploader-downloader
Bidirectional sync between Markdown and Notion. Upload .md files with images to Notion pages/databases, append to existing pages, or download Notion content back to markdown. Supports rich formatting, tables, code blocks, GitHub-flavored markdown, and recursive page hierarchy downloads with YAML frontmatter for round-trip sync.
feature-documentation
Document user-facing features in a codebase. Use when asked to document features, explain what software does, or generate feature docs. Identifies features (not technical layers), then produces numbered markdown files per feature. Works with any language.
effective-go
Idiomatic Go patterns and conventions from official Effective Go guide. Use when writing Go code to ensure proper naming, error handling, concurrency patterns, interface design, and Go-specific idioms. Triggers on Go file creation/editing, code review, or when user asks for idiomatic Go. If you cannot find any info visit to https://go.dev/doc/effective_go