ai-era-craft-and-quality-moat

name	AI-Era Craft and Quality Moat
catalog_line	Decide where craft and quality are the moat when AI makes shipping cheap: differentiation, quality bets, AI-slop diagnosis.
description	Root skill for deciding where craft and quality are the moat when AI makes shipping working software cheap. Use for "how do we differentiate" questions, prioritizing quality investments, good-enough-vs-excellent roadmap arbitration, defending craft hires against AI-substitution arguments, defining a quality north star, or diagnosing why a product feels like AI slop despite functional parity. Strategy layer above per-screen audits — distills the Saarinen/Field/Wen/Lu consensus into a craft priority ladder, a five-question surface-posture filter, a craft-vs-speed quadrant, hiring and roadmap rubrics, and BuildOS posture calls.
skill_type	strategy
altitude	meta
activation	progressive
preserve_markdown	true
legacy_paths	["ai-era-craft-and-quality-moat","docs/research/youtube-library/skill-drafts/ai-era-craft-and-quality-moat/SKILL.md"]
reference_modules	[{"id":"ai_era_craft_and_quality_moat.core_thesis_and_consensus","name":"Core Thesis & Four-Leader Consensus","summary":"The five-point consolidated argument (AI lowers the floor, taste rises in value; speed plus taste compounds; quality is strategy; the 1927 Calkins craft cycle; AI tries to outsource judgment), the Saarinen/Field/Wen/Lu claim-by-claim consensus table, and the craft-moat vs. delight-moat (Changuel) school comparison.","when_to_load":["When defending the craft posture, writing strategy or board framing, or answering \"why bet on craft\" / \"how do we differentiate\".","When choosing between the craft-moat and delight-moat schools for a product category."],"path":"references/core-thesis-and-consensus.md"},{"id":"ai_era_craft_and_quality_moat.craft_priority_ladder","name":"Craft Priority Ladder","summary":"The eight-dimension opinionated ranking of where craft still matters (taste & judgment, time-to-value, IA & opinionated defaults, performance, visual craft, component consistency, copy, accessibility) — each with what AI does well, what it does badly, where the moat lives, and the hiring implication — plus the delegate-confidently-to-AI list.","when_to_load":["When allocating craft investment across dimensions or surfaces.","When deciding what to delegate to AI versus keep under human judgment, or setting a quality north star."],"path":"references/craft-priority-ladder.md"},{"id":"ai_era_craft_and_quality_moat.decision_filter_and_failure_modes","name":"Decision Filter & AI-Era Failure Modes","summary":"The five-question \"good enough is mediocre\" surface-posture filter, the craft-vs-speed quadrant matrix, and the named AI-era failure modes (screenshot trap, Shadcn slop, component sprawl, naming inflation, eval theater, speed-as-shipping-debt, outsourced judgment, process collapse).","when_to_load":["When making a ship/cut or posture call on a specific feature, surface, or release.","When diagnosing AI slop, picking a craft-vs-speed quadrant, or running a pre-launch review."],"path":"references/decision-filter-and-failure-modes.md"},{"id":"ai_era_craft_and_quality_moat.hiring_and_roadmap_rubrics","name":"Hiring & Roadmap Rubrics","summary":"Quality as a hiring rubric (makers over specialists, critique-as-application, paid work trials, filter for taste in AI use) and quality as a roadmap framework (door test, scope reduction, internal MVP, no A/B-test crutch, 7-day zero-bug window, main quest only).","when_to_load":["When running a hiring loop, evaluating a candidate, or writing a hiring rubric.","When arbitrating a roadmap, scoping a feature, or setting release discipline."],"path":"references/hiring-and-roadmap-rubrics.md"},{"id":"ai_era_craft_and_quality_moat.buildos_application","name":"BuildOS Application","summary":"Concrete BuildOS posture decisions — anti-feed positioning as quality-as-moat, the surface triage table (brain dump / brief / structuring high-craft; settings AI-baseline), Inkprint as the craft-token enforcement layer, and BuildOS hiring and roadmap postures.","when_to_load":["When the decision concerns BuildOS specifically — its surfaces, positioning, design system, hiring, or roadmap."],"path":"references/buildos-application.md"}]
path	apps/web/src/lib/services/agentic-chat/tools/skills/definitions/ai_era_craft_and_quality_moat/SKILL.md

AI-Era Craft and Quality Moat

Identity

Use this skill to make strategic decisions about where craft is the moat in a world where AI has commoditized "shipping working software."

This is the strategy layer (meta altitude) above per-surface audits. It backs roadmap meetings, hiring loops, positioning, and board decks — it allocates craft, it does not perform the reviews. The deep frameworks live in the reference modules; the body holds the sequence, the output contract, and the escalation map.

Activation

• Prioritizing quality investments — deciding which features, surfaces, or polish work deserve disproportionate craft effort.
• Evaluating a "good enough vs. excellent" tradeoff on a roadmap arbitration.
• Defending craft hires against AI-substitution arguments ("can't an LLM do this?").
• Defining a quality north star for a small team that has to choose what to over-invest in.
• Building a moat or differentiation story in a category where every competitor now ships features at AI speed.
• Diagnosing why a product feels like "AI slop" despite functional parity with competitors.
• Setting the hiring rubric for a team in the AI era — generalist product builders vs. specialists.

Do not use this skill for per-screen visual reviews (visual_craft_fundamentals), in-app UI/UX audits (ui_ux_quality_review), calm-software restraint review of a flow (calm_software_design_review), marketing-site section audits (marketing_site_design_review), or tactical "fix this button" requests — this skill answers whether to fund the fix, not how to do it.

Judgment

The consolidated thesis: models lower the floor of shipping working code, which raises the value of taste, judgment, and design; speed without judgment produces mediocrity at scale, while speed plus taste compounds; quality is strategy, not aesthetics. Prior tech cycles outsourced labor — AI tries to outsource judgment, and the team that refuses wins the next decade.

Procedure

1. Name the decision in one sentence: ship/cut call, hire/no-hire, roadmap arbitration, positioning/differentiation framing, or slop diagnosis. If the request is actually a tactical per-screen review, escalate immediately per the map in Routing instead of running this skill.
2. When the ask is "why craft" / "how do we differentiate" — or the craft posture itself is being challenged — load ai_era_craft_and_quality_moat.core_thesis_and_consensus and anchor the argument in the five-point thesis and the four-leader consensus, including the steel-man from the delight-moat school.
3. For a posture call on a specific feature, surface, or release, load : run the five-question filter, place the product on the craft-vs-speed quadrant, and name any active AI-era failure modes by name.