pdf-analyzer
Intelligent multi-pass PDF analyzer for extracting document structure, content inventory, and metadata. Uses overview-first approach - scans for TOC, infers structure from semantics when TOC missing. Handles la...
Explorez des skills pour le développement, le contenu, les données et la productivité. Comparez les descriptions et dépôts.
Intelligent multi-pass PDF analyzer for extracting document structure, content inventory, and metadata. Uses overview-first approach - scans for TOC, infers structure from semantics when TOC missing. Handles la...
Create pull requests with gh command after development is complete. Use when ready to open a PR.
Guide technology selection workflow and ADR creation. Use when user asks about choosing a technology, comparing options, or needs to make a tech decision. Orchestrates discovery, evaluation, and documentation.
This skill should be used when user asks "/review", "검토 보고서", "검토보고", "분석 보고서", "review report", "analysis report", "법률 검토", "규제 검토", "라이선스 검토", or wants to create professional Korea...
This skill should be used when user asks "/playwright-test", "/test", "test automation", "Playwright test", "E2E test", "web test", "multi-agent test", "functional/visual/API/performance test", "테스트 자동화",...
This skill should be used when user asks "/report", "/report-writer", "보고서 작성", "report writing", "문서 작성", "DOCX 생성", "business report", "전략 보고서", "기획 보고서", "한글 보고서", "Word 문서", "pyt...
This skill should be used when user asks "/report", "/report-writer", "보고서 작성", "report writing", "문서 작성", "DOCX 생성", "business report", "전략 보고서", "기획 보고서", "한글 보고서", "Word 문서", "pyt...
Chronicle writing, research transmission, and prose lens application. Use when: writing chronicle chapters, surveying git history for chapters, transmitting research arcs, applying narrator or wanderer lenses,...
Complete visual content system. Tron-meets-Excalidraw aesthetic - dark backgrounds, neon accents, hand-drawn sketch style.
Ecology for developing ideas through concept exploration, research, and implementation. ACTIVATE for dev work: - "what's next for [app]", "continue [app]", "work on [app]" - "build [feature]", "implement [feat...
テストコードを書く・修正する前に必ず参照する。テスト作成・修正・レビュー・リファクタリング時に使用。
Angular 21 開發模式和最佳實踐
創建和維護 CMS Content Block 組件
Complete Git version control workflow automation. USE WHEN user mentions commit, push, pull request, PR, branch, merge, rebase, stash, git status, staged files, unstaged changes, OR any version control operatio...
Complete ArgoCD API and CLI skill for GitOps automation. Use when working with ArgoCD for: (1) Managing Applications - create, sync, delete, rollback, get status, (2) ApplicationSets - templated multi-cluster d...
Comprehensive skill for interacting with Grafana's HTTP API to manage dashboards, data sources, folders, alerting, annotations, users, teams, and organizations. Use when Claude needs to (1) Create, read, update...
Guide for using direnv - a shell extension for loading directory-specific environment variables. Use when setting up project environments, creating .envrc files, configuring per-project environment variables, i...
Guide for implementing 1Password secrets management - CLI operations, service accounts, and Kubernetes integration. Use when retrieving secrets, managing vaults, configuring CI/CD pipelines, integrating with Ex...
Onboard AI creativity benchmarks into HELM-compliant Scenario implementations. Use when asked to onboard a benchmark, create a HELM scenario, process a paper into evaluation code, convert a dataset to HELM form...
Ultimate Three.js development with WebGPU, React Three Fiber, performance optimization, and production-ready patterns. Use for building 3D web apps, optimizing rendering, implementing shaders, integrating physi...
Langfuseのトレース、ログ、observability、モニタリングデータを取得・表示する。ユーザーが「Langfuseのログを見せて」「トレースを確認」「観測データを取得」などと言ったときに使用する。
CodeRabbitのレビューコメントを自動修正するためのワークフロー手順です。レビュー修正の依頼があった場合に使用してください。
Gitのコミットメッセージを作成する際のルールとフォーマットを定義します。コミットメッセージを作成または提案する際に必ず使用してください。
Gitを使用した開発ワークフローのルールです。ブランチの変更、Worktreeの作成、Pull Requestの作成時に必ず確認し遵守してください。
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.