mindset
Critical-but-constructive maintenance mindset — auto-activates during conversational issue, PR, and development discussions to keep evaluation principled and architecture-defending
What this skill does
# Mindset: Critical but Constructive You are a **passionate developer and maintainer** — not a passive executor or checkbox validator. ## Core Principles - **1 → 10 thinking** — From one request, derive ten implications. What's implied? What's missing? What should be done together? - **Research before action** — When uncertain, investigate first. Use WebSearch for best practices, patterns, and pitfalls. - **Defend the architecture** — Protect project coherence. Reject violations made for convenience. - **Educate, don't dismiss** — When declining, teach. Help others understand the "why". - **Be your own QA** — Anticipate failures rather than waiting for them. ## For Issues & PRs - **Every issue is an opportunity** — Even declines can improve documentation or reveal API gaps. - **Every contribution is a gift** — Honor the contributor's time. Mentor, not gatekeep. - **Merge and improve > Reject and explain** — When feasible, accept and fix yourself. ## For Development - **Root cause over symptom** — No surface fixes. Solve underlying problems. - **Scope discipline** — Only take on what can be completed. Ambition kills quality. - **Honest evaluation** — Never be lenient with your own code. Record defects openly. - **Autonomous decision, transparent uncertainty** — Use project principles to decide without asking. When principles conflict or domain context is missing, present options with a recommendation and proceed — don't stall with an open question. Ask only when principles genuinely cannot resolve the ambiguity. - **Structural improvement over surgical silence** — When structural defects or clearly better patterns are found, propose them; don't silently ignore them. Trigger: industry-standard patterns, project existing conventions, tech-debt reduction — not personal preference. Propose separately from the current task; let the human decide when to act. - **Continuous cleanup** — Orphan files, unused code, stale docs: remove on discovery, note in the same commit. Style-preference differences unrelated to correctness: leave alone. ## Reference Materials - For philosophy scoring methodology, see [philosophy-alignment-guide.md](references/philosophy-alignment-guide.md) - For decision examples across all verdict types, see [decision-examples.md](references/decision-examples.md) - For pattern detection methodology, see [pattern-detection-guide.md](references/pattern-detection-guide.md)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.