Browse 182,092 skills across 14 categories.
Writes technical blog posts with professional yet friendly tone
Guidelines, research patterns, diagram standards, and publishing workflows for creating technical blog posts on yogendra...
対象技術の最新情報を調査し、技術調査レポートを作成する
Guide to negotiating technology services agreements, professional services contracts, and commercial B2B transactions. P...
Contract Review for Tech and general contract. Smart redflagging feature to show the problems.
Run a structured technical debt scan across the STG codebase with prioritized findings
Identify, document, score, and prioritize technical debt into an actionable backlog. Use when: tech debt, code smell, TO...
Systematic tech debt inventory with cost model. Each item gets weekly cost, incident risk, blast radius, and fix effort....
Review and prioritize technical debt
This skill should be used when the user asks to "find dead code", "remove unused code", "clean up tech debt", "find dupl...
Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the cod...
Scan, record, prioritize, or report technical debt in the game project.
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt regist...
Scans and prioritizes tech debt and code-health cleanups. Use when asking what to clean up, assessing code health, plann...
Identify and resolve technical debt with focus on finding and cataloging issues. Use when asked to find code smells, aud...
Document and prioritize technical debt. Use when the user says "tech debt", "legacy code", "this code is a mess", "refac...
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
Use when reworking a change to prevent tech debt, or auditing existing debt to categorize, score, and prioritize the ref...
Technical debt management - scan codebase for bad smells and create tracking issues
扫描并按优先级排序技术债务，覆盖设计、实现、依赖、测试四类债务的分类与跟踪。
Analyze and prioritize technical debt with refactoring recommendations. Use when evaluating code quality or planning deb...
This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technic...
Technical debt identification, quantification, and prioritization for informed remediation planning
Audit a whole repository or subsystem for technical debt with at most four non-overlapping read-only subagents, lead ver...
Automated Phase 4 technical debt capture and Ticket creation. Parses work-log evaluation reports, extracts TD (Technical...
Detect technical debt patterns in code including duplication, complexity, and maintainability issues. Use at phase check...
Tech-debt narrator: finds suppress comments, TODOs, empty catches, workarounds, legacy imports, and type-loosening patte...
Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.
Turns loose complaints about messy code into a ranked, costed technical debt backlog. Finds debt in incidents, churn, re...
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarter...
Systematic technical debt reduction and code optimization agent. Use when refactoring code, reducing complexity, elimina...
Loop automatizado de melhoria contínua que usa o Chat RAG para identificar débitos técnicos, implementa correções, reing...
Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when us...
Skill d'identification et de priorisation de la dette technique dans un projet. Scanne les patterns de dette (TODO/FIXME...
Track, prioritize, and pay down technical debt systematically in ANY project
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we r...
This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야...
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis",...
Draft, review, pressure-test, compare, and polish technical design documents for product, API, SDK, infrastructure, stor...
Generates professional Technical Design Documents following industry-standard engineering practices. This skill activate...
Erfasst lokale Hardware, Software- und Python-Versionen mit Quellenbelegen als privaten, versionierten Techshot und verg...
Generate technical architecture diagrams, pipeline flows, layer/stack diagrams, and system illustrations as standalone H...
Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions
技术协作场景下撰写与维护高质量技术文档的统一写作指南。
Expert technical document reviewer. PROACTIVELY review ADRs, Design Docs, and RFCs for quality, completeness, and princi...
在撰写、改写、校对或审阅中文技术文档、产品文案、界面文案、Markdown 文档、API 说明、操作手册、故障排查或运维文档时使用。采用克制、准确、可扫读的中文技术写作风格；保留原文事实、限制和机器可读内容；按任务读取术语排版、API 状态...
This skill should be used when writing or reviewing technical documentation such as READMEs, API documentation, quicksta...
Search internal technical documentation, ADRs, RFCs, runbooks, architecture guides, and deployment procedures. Use when...
Technical documentation writing skill covering API docs, architecture documentation, deployment guides, and various tech...
Drizzle ORM schema design, query building, and migration patterns. Extends platform-database with Drizzle-specific rules...
Technical due diligence for M&A, investment, or acquisition. Reads a target company's codebase and generates a comprehen...
A reasoning lens for technology strategy — where value moves when a technology shifts, who already holds distribution, w...
This skill should be used when users request comprehensive analysis of technology ecosystems, comparing multiple librari...
将复杂的技术概念简单化，编写教程、指南和学习路线图
Big tech ML engineer to indie founder transition coach. Expert in idea validation, MVP development, marketing, monetizat...
Technology assessment frameworks and evaluation methodologies
Use this skill when the user asks to humanize, rewrite, de-AI, polish, or detect AI writing in documents, emails, chat m...
Write mechanism-first technical implementation deep-dive articles for system/design/code explanations. Use when users as...
iOS and Swift development patterns. Extends platform-mobile with iOS-specific rules. See swift-concurrency skill for asy...
Technical lead bridging architecture and implementation for code quality and guidance. Use when reviewing code, refactor...
Principal Tech Lead (Architect + DevOps + Fullstack) - System design, code architecture, infrastructure, implementation....
技术负责人专家，精通技术架构设计、技术选型、代码审查和团队技术管理
Tech Lead. Use for Phase 9 MVP implementation with TDD. Real titles: Tech Lead, Staff Engineer.
Transforma requisitos e arquitetura existente em roadmap, épicos, tickets e dependências executáveis. Use para planejar,...
Technical leadership and code review
Reference document for monopoly tech-matrix.
显式启动系统学习、刻意练习、掌握检验和阶段复盘。仅在用户明确调用 $tech-mentor 时使用；普通知识问答、一次性解释或未要求建学习计划时不要隐式触发。
Structures a technical paper's full logical skeleton using a thinking-template table (research background, limitations,...
Prisma ORM schema design and query patterns. Extends platform-database with Prisma-specific rules. Use when working with...
Build production-grade landing pages for software/CLI tools, developer libraries, and technical products. Uses the "Maxs...
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants follo...
Use when choosing or evaluating a technology (framework, database, library, cloud tool) — injects Tikal Israeli Tech Rad...
React-specific component, hook, and rendering patterns. Extends platform-frontend with React rules. Use when writing Rea...
React Native development patterns. Extends platform-mobile and tech-react with React Native-specific rules. Use when bui...
Generates professional technical reports from performance analysis data. Creates investor and client-ready documents wit...
Enforces iterative web research for coding and DevOps questions to prevent assumptions about libraries, frameworks, APIs...
优化技术类简历，覆盖软件工程、产品经理（PM）及技术岗位，适用于 tech resume、SWE resume、developer resume 等场景
技術ブログ記事、チュートリアル、技術原稿を、技術的正確性、一次情報、現在の API 挙動、コード、再現性、セキュリティ、アクセシビリティ、互換性の観点からレビューする。技術的な主張、コードサンプル、対応バージョン、仕様、公開前の正確性を確認...
Run a senior tech lead review of Pieceful's design docs, save the findings to the private notes, and walk the owner thro...
Turn a technical design doc into a product/QA-readable technical review markdown (business language + Mermaid). Hard-gat...
技术卡片审核。验证问题卡片/知识卡片的准确性，查找资料核实，指出错误并提供改进建议。当用户说「review」「审核」「检查」技术文档时使用。适用于 tech/ 目录。
Expert technology scouting including emerging tech discovery, evaluation, and adoption recommendations
Self-contained deep tech research. WebSearch + WebFetch + Haiku workers. Pipeline: Query > Decompose > Parallel Search (...
将技术选型决策转换为业务语言解释，生成客户友好的技术说明。当ARCH中技术术语过多、需要向PM/客户解释时使用。
Run technical SEO audit. Use when: checking Core Web Vitals, crawlability, indexation, speed, or structured data.
生成"三下乡社会实践-科技服务类"立项申报书 docx。覆盖科技服务、医疗服务、法律援助、农业技术指导四类子方向，含服务对象需求清单、专业能力匹配矩阵、按服务场次实施方案表（场次/日期/地点/对象/服务内容/人数/专业要求）、服务流程设计、...
Technical presentation / talk slides as HTML. Code snippets, diagrams, speaker notes. Use for "tech talk", "tech sharing...
[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Gener...
[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/...
Produces implementation-ready technical specifications with concrete contracts, module boundaries, data flows, file chan...
- Keywords: tech spec, technical specification, spec review, review spec, requirement analysis, feature design
Show Tech Spec details or update status through lifecycle
Create comprehensive technical specification documents through interactive Q&A. Use when (1) user asks to write a Tech S...
Write implementation-ready software technical specifications for senior engineers.
The master skill for generating technical specifications. Identifies project technology and delegates deep analysis to s...
Update the related tech specs and requirements as part of planned work. Invoke only when explicitly called by user.
技術検証（Tech Spike）ワークフロー。ライブラリ選定やアーキテクチャ判断の前に最小限の実験コードで技術的妥当性を検証。使用タイミング:(1) 複数の技術選択肢がある場合（ライブラリA vs B）(2) 新しいライブラリ・技術の学習コ...
Describes the primary technologies, frameworks, libraries, and language conventions used in this codebase.
Advise on technology stack selection, architecture decisions, and tooling trade-offs — grounded in team context, scale r...