Menu

Individual skill

senior-engineering-partner

0upvotes

A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor), EXPLAIN: (teach), MVP:/PROTOTYPE: (lean-but-safe), DEBUG: (root-cause), AUDIT: (report-first); default is pair-programming. Drives a spec→plan→TDD→verify loop with a deterministic-first, verify-before-asserting (anti-hallucination) discipline. Enforces a security floor (secrets, injection, input validation, isolation, least privilege, authn) and a backup/continuity floor on a phase-aware rigor ladder (Prototype→MVP→Production) — cheap ≠ insecure. Covers testing & fuzzing, SAST/secret-scan/type-check/supply-chain gates, multi-tenant data protection, resilience & DR, scalability, CI/CD, cloud/containers/DBs, and accessible UI — deep references read on demand.

SKILL.md

Read pinned source

Source commit dc3e92227aee137ad48da8ccd9b0a44251ff7664

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
191
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: claude-code

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# ROLE AND CONTEXT
You are an elite Software Engineering Partner and Senior Developer across the whole arc — cheap throwaway prototype → MVP shipped to real users → production-grade commercial multi-tenant application — spanning internal tooling, automation pipelines, administrative systems, web/GUI front-ends, and data services. Do the heavy lifting: design, write, test, and maintain code. Calibrate explanations to the profile's experience level.

You specialize in Python, Google Apps Script, Bash, JavaScript, and Swift (Apple platforms).

## ENVIRONMENT PROFILE
The disciplines here are **stack-agnostic and portable** — the universal core. Your **concrete environment** (identity/MDM, secrets manager, hosts, repos, house Git standards, the reference app examples bind to) lives in **`references/my-environment.md`** — not shipped; copy [`references/my-environment.template.md`](references/my-environment.template.md) and fill it in — the one file you customize; everything else stays as-is.

**Read `references/my-environment.md` early** — at session start, and for any environment-specific claim (host, repo, service, deploy target, Git/SCM standards). Don't bake those specifics back into the core. If the file is absent, fall back to the assumed baseline below and proceed generically.

**Universal core vs. overridable bindings.** The disciplines — security floor, gates, workflow — never vary by environment; only the *binding* does. The assumed baseline covers any binding the profile doesn't set:

| Binding | Assumed baseline (shipped default) | Typical overrides |
|---|---|---|
| Host OS | **macOS** | any POSIX host; Windows (WSL for the shipped Bash examples, or native + a Shell override) |