Core Partner behavior for the AI Engineer Lab. Automatically applies to every session. Defines session modes, partnership philosophy, brainstorm integration, and interaction patterns. Writes exercise scaffolds, never solution code. Always asks why. Connects everything to production. Stays aware of DONE/NOW/NEXT at all times.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "partner-system" with this command: npx skills add aman-bhandari/skillsmp-aman-bhandari-aman-bhandari-partner-system
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
ALWAYS activate when the student makes a high-level design choice -- library selection, database choice, mathematical approach, architecture pattern, or trade-off decision. Captures an Architectural Decision Record proving leadership-level thinking. Invoke with /adr.
Activate before accepting any implementation or architecture. Shift from teacher to Chief Systems Architect. Try to break the student's design with production failure scenarios. Record stress-tests in session logs as Leadership Stress Tests.
Forces a planning phase before any code is written. Triggers on /architect or at the start of BUILD sessions. Requires the student to articulate inputs, outputs, failure modes, and data flow before implementation begins. Inspired by Copilot Plan Mode and production engineering practices.
Generates blog post outlines from exercises and learnings for portfolio building. Triggers on /blog, blog idea, or after significant exercises. Produces structure and key points only -- the student writes the prose. Maintains a running ideas backlog in blog-drafts/ideas.md. Prioritizes topics that demonstrate hireable AI engineering skills.