cc-c-project-standard
Use when Pure C module interfaces, ownership contracts, error-code cleanup paths, build conventions or C engineering validation…
Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review.
Claude Code
$ npx -y skills add bovinphang/frontend-craft --skill cc-python-project-standard --agent claude-code
Codex
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a codex -y
Cursor
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a cursor -y
Gemini CLI
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a gemini-cli -y
GitHub Copilot
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a github-copilot -y
OpenCode
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a opencode -y
Windsurf
$ npx skills add bovinphang/frontend-craft --skill cc-python-project-standard -a windsurf -y
name: cc-python-project-standard description: "Use when Python package layout, pyproject conventions, typing, import-time behavior, dependency boundaries or repository-wide Python quality checks need design or review."
Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
Read pyproject, lock/environment conventions, supported Python versions and current package layout. Do not mix new installers or replace the environment implicitly.
1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now. 2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change. 3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result. 4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
Focused event-loop cancellation or blocking-I/O problems belong to the async specialty.
Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.
Use when Pure C module interfaces, ownership contracts, error-code cleanup paths, build conventions or C engineering validation…
Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++…
Use when diagnosing unexplained engineering failures, build errors, service exceptions, inconsistent data, or cross-layer faults…
Use when project documentation, multilingual READMEs, setup instructions, CLI usage, or public capability descriptions drift from…
Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML,…
Use when an Electron application needs work on main/preload/renderer boundaries, contextBridge IPC, sender validation, sandbox…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.