skills/curated/extreme-software-optimization/SKILL.md
Profile-driven performance optimization with behavior proofs. Use when: optimize, slow, bottleneck, hotspot, profile, p95, latency, throughput, or algorithmic improvements.
npx skillsauth add pedronauck/skills extreme-software-optimizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The One Rule: Profile first. Prove behavior unchanged. One change at a time.
1. BASELINE → hyperfine --warmup 3 --runs 10 'command'
2. PROFILE → cargo flamegraph / py-spy / clinic flame
3. PROVE → Golden outputs + isomorphism proof per change
4. IMPLEMENT → Score ≥ 2.0 only, one lever per commit
5. VERIFY → sha256sum -c golden_checksums.txt
6. REPEAT → Re-profile (bottlenecks shift)
| Hotspot | Impact (1-5) | Confidence (1-5) | Effort (1-5) | Score | |---------|--------------|------------------|--------------|-------| | func:line | × | × | ÷ | Impact×Conf/Effort |
Rule: Only implement Score ≥ 2.0
For EVERY change, document:
## Change: [description]
- Ordering preserved: [yes/no + why]
- Tie-breaking unchanged: [yes/no + why]
- Floating-point: [identical/N/A]
- RNG seeds: [unchanged/N/A]
- Golden outputs: sha256sum -c golden_checksums.txt ✓
| Pattern | When | Isomorphism | |---------|------|-------------| | N+1 → Batch | Sequential fetches | Same results, fewer round-trips | | Linear → HashMap | Keyed lookups | O(n)→O(1), order may change | | Lazy eval | Maybe-unused values | Same final values | | Memoization | Repeated pure calls | Cached = recomputed | | Buffer reuse | Alloc per iteration | Zero-copy in loop |
| Pattern | Change | Check | |---------|--------|-------| | Binary search | O(n)→O(log n) | Sorted input | | Two-pointer | O(n²)→O(n) | Structured input | | Prefix sums | O(n)→O(1) query | Static data | | Priority queue | O(n)→O(log n) | Top-k/scheduling |
| Structure | Use Case | |-----------|----------| | HashMap | Point lookups | | BTreeMap | Range queries | | SmallVec | Usually-small collections | | Arena | Many allocations, bulk free | | Bloom filter | Membership pre-filter |
Full catalog: TECHNIQUES.md
| Lang | CPU Profile | Trouble Spot Grep |
|------|-------------|-------------------|
| Rust | cargo flamegraph | rg '\.clone\(\)' --type rust |
| Go | go tool pprof /debug/pprof/profile | rg 'interface\{\}' --type go |
| TS | clinic flame -- node app.js | rg 'JSON\.(parse\|stringify)' --type ts |
| Python | py-spy record -o flame.svg -- python script.py | rg '\.iterrows\(\)' --type py |
Full language guides: LANGUAGE-SPECIFIC.md
| ✗ | Why | |---|-----| | Optimize without profiling | Wastes effort on non-hotspots | | Multiple changes per commit | Can't isolate regressions | | Assume improvement | Must measure before/after | | Change behavior "while we're here" | Breaks isomorphism guarantee | | Skip golden output capture | No regression detection |
git revert <sha># Benchmark
hyperfine --warmup 3 --runs 10 'command'
# Profile
cargo flamegraph # Rust CPU
heaptrack ./binary # Allocation
strace -c ./binary # Syscalls
# Verify
sha256sum golden_outputs/* > golden_checksums.txt
sha256sum -c golden_checksums.txt # After changes
| Need | Reference | |------|-----------| | Complete technique catalog | TECHNIQUES.md | | Step-by-step methodology | METHODOLOGY.md | | Language-specific guides | LANGUAGE-SPECIFIC.md | | Advanced (Round 2+) | ADVANCED.md |
Each round: fresh profile → new hotspots → new matrix.
development
Guides a founder through the full Y Combinator batch application end-to-end. A 10-phase workflow that captures the live YC form, profiles the founders, stress-tests the idea via an embedded grill loop, runs a mandatory 5-agent parallel external research pass on the startup, drafts every form field with anti-pattern and accepted-example checks, produces founder-video bullet notes (no script), runs a final adversarial gate, generates paste-ready submission answers, unlocks an interview-prep simulator after invite, and supports reapplicant delta tracking and post-decision post-mortems. Writes a documented markdown trail under a user-chosen workspace. Use when a founder wants to prepare a YC batch application, build their founder video, drill mock YC interview questions, or reapply with delta evidence. Don't use for pitch-deck design unrelated to YC, generic startup advice without applying, or post-funding work.
development
Authors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
tools
Provides guardrails for user-facing UI work: usability heuristics, accessibility floors, design-system discipline, component states, microcopy, motion, dark mode, responsive behavior, and human-AI UX. Use when designing, generating, reviewing, or refactoring visible product surfaces such as components, pages, dashboards, forms, dialogs, loading/empty/error states, or AI interfaces. Do not use for backend-only work, infrastructure, CLI/TUI design, or pure documentation editing.
tools
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects. Don't use for plain JavaScript, runtime validation libraries (Zod, Yup), or basic TypeScript syntax questions.