fasalzein
- 15 skills
- 0 followers
- 1 day ago last updated
- ▌ Research · fasalzein bundleAutonomous deep research on any topic. Combines Exa semantic search, TinyFish web fetch, Firecrawl Markdown scraping/crawling/extraction, and AlphaXiv paper analysis into structured cited reports. Use when: research this, deep research, deep-research, find out about, what's the latest on, deep dive into, investigate, analyze the landscape of, compare approaches to, literature review, state of the art, how does X work. Produces a structured research report with citations.
- ▌ Desloppify · fasalzein bundleCode quality scanner. Detects AI-introduced anti-patterns across many categories. Run the CLI, triage results, fix on isolated git worktrees. Trigger: desloppify, clean up code, remove slop, code quality, dead code.
- ▌ To Slices · fasalzeinSlice a PRD or plan into independently-grabbable vertical slices — tracer bullets, each with acceptance criteria — for an implementing agent to pick up. Use when the user wants to turn a PRD or plan into implementation tickets, or plan delivery work.
- ▌ Design QA · fasalzein bundleBinary pass/fail quality gates for UI code — run before shipping any component, page, or feature. Use when the user asks to QA, audit, review, or harden UI, before merging UI work, or after any design implementation to verify it. Covers anti-slop, accessibility, consistency, interaction states, performance, responsive, and live in-browser verification.
- ▌ Laws Of UX · fasalzeinUser-psychology rules for UX decisions — cognitive load, attention, memory, mental models, motor cost, perception. Use when choosing nav structure, form length, decision flows, error recovery, onboarding, progress indicators, or microcopy, or when a flow feels confusing, overwhelming, or hard to complete. Complements design-craft (craft) with the WHY (psychology).
- ▌ Design Craft · fasalzein bundleAnti-slop UI craft rules that break out of the AI-generated median. Use when building or restyling any UI — pages, components, dashboards, forms, landing pages — when existing UI looks generic or machine-made, or when another skill needs rules for typography, color, spacing, layout, composition, motion, product states, or interaction.
- ▌ Tdd · fasalzein bundleBehavior-first red-green-refactor testing. Use when building features, fixing bugs, or needing integration tests.
- ▌ Wiki · fasalzeinWiki vault memory — retrieval, freshness, research, handovers. Use when the user says wiki, asks about vault, project memory, or knowledge context.
- ▌ Forge · fasalzeinForge tracked lifecycle for features, slices, evidence, review, and close. Use when the user says forge, plans features, runs slices, or closes delivery work.
- ▌ Diagnose · fasalzein bundleDisciplined diagnosis loop for bugs and performance regressions. Use when debugging failures, broken behavior, crashes, or slow paths.
- ▌ Handover · fasalzeinCompact current work into a next-agent handover. Use when ending a session, the user says handover, transferring work, or preserving continuity.
- ▌ Write A Prd · fasalzeinSynthesize current context into a Forge PRD. Use when the user wants a PRD, product spec, or plan captured for delivery.
- ▌ Prd To Slices · fasalzeinBreak PRDs into tracer-bullet Forge slices. Use when converting plans, specs, or PRDs into implementation slices.
- ▌ Grill With Docs · fasalzein bundleStress-test plans against domain language and ADRs. Use when sharpening terminology, validating plans, or recording architecture decisions.
- ▌ Improve Codebase Architecture · fasalzein bundleFind deepening refactors that improve leverage, locality, and tests. Use when reviewing architecture, seams, modules, or coupling.