Private House Code
Use for every task that plans, writes, edits, debugs, tests, refactors, reviews, or maintains code. Apply to professional repositories, scripts, apps, services, prototypes, beginner work, vibe coding, and bounded code changes inside large systems. Choose the fewest clear lines, files, paths, states, and abstractions that correctly implement the requested behavior. Do not invent fallbacks, compatibility paths, defensive layers, or future scale without evidence. Do not use for ordinary conversation, emotional support, prose, translation, summarization, social-media content, or general research o
Install
npx skills add See-Sol-Lab/private-house-code-v2.5 --skill private-house-codegit clone --depth 1 https://github.com/See-Sol-Lab/private-house-code-v2.5.git /tmp/private-house-code-v2.5
mkdir -p ~/.claude/skills
cp -r /tmp/private-house-code-v2.5/. ~/.claude/skills/private-house-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Private House Code Write the feature. Do not build a bank around it. For coding tasks, build the **smallest complete implementation**: correct at its real boundaries, obvious to a human maintainer, aligned with the current project, and no more complex than the requested behavior requires. **Every added line, file, abstraction, state, path, dependency, process, check, and fallback must have a present job.** ## 1. Apply only to coding, then take the direct path If the current task does not plan, change, test, review, or maintain code, do not apply the remaining instructions. For coding work: - Start from the requested behavior, not an imagined architecture. - If one readable line is enough, write one readable line. If one ordinary function is enough, do not create a class, interface, service, manager, adapter, or factory. - When several designs are equally correct, choose the one with fewer moving parts overall, not merely fewer lines. A shorter implementation is not simpler if it introduces a heavier persistence model, resource lifecycle, migration burden, test scaffolding, or failure modes the current task does not need.
Details
- Skill name
private-house-code- Repository
- See-Sol-Lab/private-house-code-v2.5
- Repo updated
- 7 September 2026
FAQ
What does the Private House Code skill do?
Use for every task that plans, writes, edits, debugs, tests, refactors, reviews, or maintains code. Apply to professional repositories, scripts, apps, services, prototypes, beginner work, vibe coding, and bounded code changes inside large systems. Choose the fewest clear lines, files, paths, states, and abstractions that correctly implement the requested behavior. Do not invent fallbacks, compatibility paths, defensive layers, or future scale without evidence. Do not use for ordinary conversation, emotional support, prose, translation, summarization, social-media content, or general research o
How do I install the Private House Code skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add See-Sol-Lab/private-house-code-v2.5 --skill private-house-code. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Private House Code popular?
It lives in See-Sol-Lab/private-house-code-v2.5, which has 96 GitHub stars and 2 forks.
Related skills
Code Humanizer
90LeonardNJU/code-humanizer
Use when AI-written code needs structural cleanup or when implementing a change under a guard against AI coding slop — duplicated reimplementations of existing helpers, try-import fallbacks, broad exception swallowing, speculative abstraction layers, _v2 copies, dead "for future use" code, narrating comments — including requests to "deslop", "remove AI slop", "humanize code", review an AI-generated PR beyond tests passing, or prevent these patterns in the current change.
Rails Upgrade Assistant
85maquina-app/rails-upgrade-skill
Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 7.0 through 8.1.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes.
Proteus Skills
99kudoumakoto6523-design/proteus-skills
使用 proteus-automatic-api Python 库创建、编辑和验证真实 Proteus/ISIS 工程，加载 MCU 固件、操作按钮/开关并读取仿真结果。用于用户要求 Proteus Skills、操作 .pdsprj、Proteus 自动化或在 Proteus 中测试按钮驱动电路的任务；普通电路讲解和概念配图不需要此技能。
Arkts Syntax Assistant
88SummerKaze/skill-arkts-syntax-assistant
ArkTS syntax, migration, and optimization guide for HarmonyOS/OpenHarmony development. Triggers on: .ets files, ArkTS keywords, HarmonyOS/OpenHarmony context, @ohos packages. Help with syntax reference, TypeScript migration, performance optimization, compile errors, state management, component development, and language-specific questions.
Verdikta Bounties Onboarding
48verdikta/verdikta-applications
Verdikta Bounties hot-wallet operator for Base. Can create/import Ethereum keys into an encrypted keystore (its password is never stored; it comes from VERDIKTA_WALLET_PASSWORD via a secret store or a prompt), keep an API key, upload public bounty/work data, call the reviewed Verdikta API and Base RPC, and sign irreversible mainnet/testnet transactions within an owner spend policy. Use fresh low-balance wallets only. Commissions a verdikta-discover work-order draft when the owner approves it in chat with a line such as 'Approve <hash prefix>, payout <X> ETH, window <N>h': it binds that exact d
Using Lwc
69JanYork/llm-wiki-cli
Use when substantive project work, structural code questions, research, planning, debugging, architecture, decisions, document ingest, incident recovery, or verified context and results should survive future sessions; also when the user invokes $using-lwc or asks to search, update, repair, configure, maintain, or transfer an LWC Wiki, graph index, or portable memory archive.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.