sethdford
- 567 skills
- 0 followers
- 19 hours ago last updated
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Twin Boundary Guard · sethdford bundleProtect stated boundaries: decline, defer, and suggest scripts when overload or misalignment appears
- ▌ Twin Weekly Debrief · sethdford bundleStructured weekly reflection: wins, drains, carryovers, and next-week focus
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Twin Meeting Wingman · sethdford bundlePrep briefs, agendas, and follow-up capture before and after meetings
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Twin Voice Calibrator · sethdford bundleMirror the user's writing style from samples; avoid generic assistant cadence
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Twin Continuity Handoff · sethdford bundleSession handoffs for future-you: state, blockers, and the next concrete action
- ▌
- ▌ Twin Relationship Memory · sethdford bundleMaintain relationship context: who people are, how the user relates, and tone per contact
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Tdd Workflow · sethdford bundleRed-Green-Refactor cycle for test-first development. Write failing test, implement minimal code, refactor safely. Use when developing new features or fixing bugs in test-driven projects.
- ▌ Test Strategy · sethdford bundleCreate testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
- ▌
- ▌ Mutation Testing · sethdfordMeasuring test quality by mutating code and checking if tests catch mutations.
- ▌ Unit Test Design · sethdfordSingle-unit tests, isolation via mocks/stubs, Arrange-Act-Assert pattern, one assertion per test.
- ▌
- ▌ Cqrs Design · sethdfordSeparate command (write) and query (read) models for complex domains. Use when read/write patterns diverge significantly or when audit/consistency requirements demand immutability.
- ▌ Rfc Template · sethdfordPropose architectural changes with comprehensive RFCs. Structure feedback, document decisions, track rationale. Use when proposing major architecture changes or design patterns.
- ▌ Empathy Map · sethdfordBuild a 4-quadrant empathy map (Says, Thinks, Does, Feels) to synthesize user research into actionable insights. Use when you need to quickly capture and share user understanding across the team.
- ▌ Journey Map · sethdfordCreate an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.
- ▌
- ▌
- ▌ QA Onboarding · sethdfordExpert approach to qa-onboarding in QA operations. Use when working with .
- ▌ User Persona · sethdfordCreate refined user personas from research data with demographics, goals, frustrations, and behavioral patterns. Use when synthesizing user research into actionable persona profiles for design decisions.
- ▌ Function Design · sethdfordDesigning pure functions with single purpose, minimal parameters, clear side effects, and high cohesion.
- ▌ Test Data Management · sethdfordCreating and managing test data via fixtures, builders, factories, and minimal realistic datasets.
- ▌
- ▌ Risk Scoring · sethdfordQuantify risk using likelihood and impact, apply severity ratings, and prioritize mitigations. Use when prioritizing threats, allocating security budget, and communicating risk to leadership.
- ▌ Build Vs Buy · sethdfordSystematically evaluate whether to build a solution or buy/use existing product. Use when evaluating tooling, services, or frameworks.
- ▌ Interface Design · sethdfordDesigning minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
- ▌ Solid Principles · sethdfordSOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
- ▌
- ▌ Root Cause Analysis · sethdfordFive Whys, fishbone diagrams, identifying systemic causes not just symptoms.
- ▌ Git Workflow · sethdfordFeature branches, commit hygiene, rebasing vs. merging, and collaborative workflows.