All authors
Claude Skills by robisson
github.com/robisson29 skills0 installs4 views
- Api Contract FirstDesigning APIs contract-first with backward compatibility guarantees, clear versioning strategy, error semantics, idempotency, and pagination. The API is a promise—never break existing clients.Votes: 0GitHub stars: 15
- Brownfield DiscoveryReverse-engineer an existing project to produce a Design Doc, API contracts, and a Threat Model anchored in the real code, IaC, and observability. Run once per project. Output anchors all subsequent /spec and /build invocations.Votes: 0GitHub stars: 15
- Code Review Bar RaisingApplying Amazon's raise-the-bar principle to every code review. What reviewers look for — clarity, correctness, design, reuse, operational readiness. "Ship It" means the change raises or maintains the quality bar.Votes: 0GitHub stars: 15
- Correction Of ErrorsBlameless post-incident analysis focused on timeline, 5 Whys, mechanisms over people, and concrete action items with owners.Votes: 0GitHub stars: 15
- Dependency ManagementManaging external dependencies safely with circuit breakers, timeouts, retries with exponential backoff, bulkhead pattern, graceful degradation, and dependency isolation.Votes: 0GitHub stars: 15
- Design DocumentWriting a technical design document that translates a Working Backwards output into a concrete, reviewable engineering plan with architecture, trade-offs, cost estimation, and operational concerns.Votes: 0GitHub stars: 15
- Design ReviewReview a technical design before specs or implementation. Evaluate problem clarity, requirements, alternatives, trade-offs, architecture, dependency behavior, security, operations, cost, testability, and simplicity.Votes: 0GitHub stars: 15
- Feature Flag LifecycleComplete lifecycle of feature flags from creation through gradual rollout to cleanup, including kill switches and A/B testing.Votes: 0GitHub stars: 15
- Implementation MemoryInternal /build flow mechanism that maintains fixed-size procedural memory of durable implementation-quality lessons.Votes: 0GitHub stars: 15
- Incremental ImplementationImplementing features in thin vertical slices that each deliver value independently. Feature flags, safe defaults, rollback-friendly changes. Never a big-bang deployment.Votes: 0GitHub stars: 15
- Infrastructure As CodeCDK/CloudFormation design principles for immutable infrastructure, environment parity, least privilege, tagging strategy, and cost optimization. Infrastructure is code—it deserves the same rigor as application code.Votes: 0GitHub stars: 15
- Mechanism CreationTurning lessons learned into automated mechanisms that prevent recurrence of problems.Votes: 0GitHub stars: 15
- Metrics ReviewReviewing operational and business metrics for continuous improvement, trend analysis, and proactive issue detection.Votes: 0GitHub stars: 15
- Operational CodeWriting code with built-in observability from day one. Structured logging (JSON), metrics emission (latency p50/p99, error rates), alarm-ready code, request tracing, graceful degradation.Votes: 0GitHub stars: 15
- Operational ExcellenceDashboards, alarms, and runbooks that make a service operable. Covers latency, error rate, availability, throughput, and severity-based alarming.Votes: 0GitHub stars: 15
- Operational Readiness ReviewThe ORR process — a self-assessment checklist covering monitoring, alarming, runbooks, on-call, scaling, security, deployment safety, cost, and dependencies. Must pass before launch.Votes: 0GitHub stars: 15
- Pipeline SafetyCI/CD pipeline safety with automated gates, deployment blockers, alarm checks, and one-click rollback.Votes: 0GitHub stars: 15
- Progressive DeploymentDeploy changes incrementally through expanding blast radius stages with bake time and automatic rollback on alarm.Votes: 0GitHub stars: 15
- Spec Driven ImplementationBridge between an approved Design Document and code. Decompose the system-level blueprint into N vertical specs (requirements → design → tasks), each independently deliverable. Fail fast by ordering hardest-first. Execute wave-by-wave with approval gates.Votes: 0GitHub stars: 15
- Test Driven DevelopmentRed-Green-Refactor cycle with Amazon's test pyramid (80% unit, 15% integration, 5% e2e). Coverage gates, DAMP over DRY in tests, canary tests in production.Votes: 0GitHub stars: 15
- Threat ModelingSecurity threat modeling using STRIDE methodology adapted for cloud services. Covers data classification, IAM boundaries, encryption requirements, blast radius analysis, and systematic identification of attack vectors before code is written.Votes: 0GitHub stars: 15
- Using Amazon SkillsMeta-skill for navigating and applying the complete skills library. Routing flow chart, core operating behaviors, and skill discovery logic.Votes: 0GitHub stars: 15
- Wb DefineStage 2 of Working Backwards: Articulate the customer's problem or opportunity with precision, using data to quantify impact and framing it in the customer's language — not engineering jargon.Votes: 0GitHub stars: 15
- Wb InventStage 3 of Working Backwards: Generate multiple solution approaches, classify decisions as one-way vs two-way doors, evaluate alternatives against customer benefit and feasibility, and select the recommended solution with clear rationale.Votes: 0GitHub stars: 15
- Wb ListenStage 1 of Working Backwards: Identify who the customer is and gather deep insights about their current experience, pain points, and unmet needs through systematic observation and data collection.Votes: 0GitHub stars: 15
- Wb RefineStage 4 of Working Backwards: Write the PR/FAQ — a press release announcing the product as if it already exists, plus a comprehensive FAQ addressing hard questions. This is the core Amazon mechanism that forces clarity, customer-centric thinking, and rigorous pre-mortems before any code is written.Votes: 0GitHub stars: 15
- Wb Test And IterateStage 5 of Working Backwards: Define how success will be measured using input and output metrics, set specific numeric targets, design experiments to validate assumptions, and plan iteration cycles based on data feedback.Votes: 0GitHub stars: 15
- Working BackwardsEntry point for developing new products, features, or initiatives using Amazon's Working Backwards process. Orchestrates 5 stages from customer insight to measurable success, starting with the 5 Customer Questions as a lightweight on-ramp before committing to a full PR/FAQ.Votes: 0GitHub stars: 15
- BlaBuild Like Amazon — the entry point for the BLA engineering flow. Routes a request to the right phase: Working Backwards discovery (wb, listen, define, invent, refine, test-idea), brownfield onboarding (onboard), design (design, spec), implementation (build, review), release (deploy, operate) and post-incident learning (learn). Use when the user types /bla, names a BLA phase or command, asks which phase or skill applies, starts a new product or feature, onboards an existing codebase, plans or...Votes: 0GitHub stars: 15