Code readability review based on "The Art of Readable Code" and Miller's Law (7±2). Use when reviewing code clarity, improving naming, or when user mentions 可読性, 理解しやすい, わかりやすい, 明確, 命名, 変数名, 関数名, ネスト, 深いネスト, 関数設計, コメント, 複雑, 難しい, 難読, Miller's Law, ミラーの法則, 認知負荷, AI-generated, 過剰設計.
Kotlin/Compose coding standards reference. This skill defines mandatory coding conventions for Kotlin and Compose code generation. All Compose-related skills MUST reference these standards. Use when: (1) Generating Compose code, (2) Reviewing Compose code, (3) Checking coding standards. Triggers: "coding standards", "compose standards", "kotlin standards", "style guide".
Ensures code quality through reviews, refactoring, technical debt management, and clean code practices
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with strict discipline against rationalization.
Comprehensive Python engineering guidelines for writing production-quality Python code. This skill should be used when writing Python code, performing Python code reviews, working with Python tools (uv, ruff, mypy, pytest), or answering questions about Python best practices and patterns. Applies to CLI tools, AI agents (langgraph), and general Python development.
Use when writing TypeScript with strict mode - covers type definitions, generics, and declaration files
Obsidian 플러그인 코드가 공식 가이드라인을 준수하는지 검토하고 개선점을 제안한다. Use when: - 사용자가 Obsidian 플러그인 가이드라인 준수 여부를 확인하고 싶을 때 - 플러그인을 커뮤니티 스토어에 제출하기 전 검토가 필요할 때 - 코드 품질, 보안, 성능, UI/UX 검토가 필요할 때 - "가이드라인", "정책 검토", "코드 리뷰", "policy review" 등의 키워드가 언급될 때 - README에 필수 공개 항목을 추가해야 할 때
Create a new rule file in .deepwork/rules/
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews. Activates on phrases like "implement this feedback", "address review comments", "fix review issues", "apply these suggestions", or when user pastes reviewer notes.
Systematically identify and remove unused imports, variables, and dead code from TypeScript/React projects using --noUnusedLocals and --noUnusedParameters compiler flags
Author or update Locque .lq code and tests with the canonical M-expr syntax, CBPV rules, data/match forms, modules/imports/opens, and project conventions.
评审 Project Guardrails/工程规范。用于在 LLD/实现前检查 Guardrails 的完整性、可执行性、一致性与可验证性，给出准出结论。
Perform thorough code reviews with focus on security, performance, maintainability, and best practices. Use when reviewing code changes, pull requests, entire files, or codebase audits across any programming language.
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing codebases, or before critical deployments.
Write TypeScript code following best practices. Use when developing TypeScript/JavaScript applications. Covers type safety, patterns, and tooling.
CSS, SCSS, and styling conventions. Use when writing, reviewing, or debugging styles and layouts.
Critical rules and best practices for working with markdown files.
C# code style and naming conventions based on POCU standards. Covers naming rules (mPascalCase for private, bBoolean prefix, EEnum prefix), code organization, C# 9.0 patterns. Use PROACTIVELY for C# code reviews, refactoring, or establishing project standards.
Writes Python code following FiftyOne's official conventions. Use when contributing to FiftyOne, developing plugins, or writing code that integrates with FiftyOne's codebase.
Comprehensive Rust development guidelines based on 6 months of code reviews. Use when writing Rust code, debugging Rust issues, or reviewing Rust PRs. Covers error handling, file I/O safety, type safety patterns, performance optimization, common footguns, and fundamental best practices. Perfect for both new and experienced Rust developers working on CLI tools, hooks, or production code.
Python code quality standards (PEP 8, type hints, docstrings). Use when writing Python code.
