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.
