Modern QA2026Quick Start Preparation: Turn Discovery into a Scaffolding-Ready Package — tiles
Log inJoin

Atlas 13 Browser Automation with Playwright Quick Start Preparation: Turn Discovery into a Scaffolding-Ready Package☰ Read as one page

Quick Start Preparation: Turn Discovery into a Scaffolding-Ready Package

2.1Why this chapter existsChapter 1 produced the raw customization artifacts.78 words2.2Inputs required from Chapter 1These must already exist:15 words2.3The main rule of this chapterplaywright-scaffolding.md is now the application-specific source of truth.33 words2.4What this chapter prepares Claude Code to doAfter this chapter, Claude Code should be ready to scaffold:71 words2.5Step 1 — Review the four required artifacts togetherOpen these side by side:79 words2.6Step 2 — Normalize naming before scaffoldingThe scaffolding phase gets much better when naming is normalized first.135 words2.7Step 3 — Decide the initial harness boundariesA good initial repo is not the whole universe. It is a clear starting slice.137 words2.8Step 4 — Decide the initial directory namingBefore Claude Code scaffolds, be explicit about the major top-level areas.36 words2.9Step 5 — Decide the opinionated defaultsBefore scaffolding, make these rules explicit.259 words2.10Step 6 — Prepare the root instruction strategyClaude Code reads CLAUDE.md at the start of every session. It is the most important file for shaping Claude's behavior, but it must stay…455 words2.11Step 7 — Prepare the planning systemThe first scaffold should not only create code folders. It should create an operating system for future work.129 words2.12Step 8 — Decide the initial validation gateThe initial repo should be easy to validate frequently.55 words2.13Step 9 — Decide the artifact and debugging conventionsThe scaffold should create predictable local outputs.87 words2.14Step 10 — Decide the initial CI expectationsThe first scaffold should be CI-aware even if CI is still minimal.86 words2.15Step 11 — Choose the right permission mode for scaffoldingClaude Code has several permission modes that control how often it pauses to ask for approval. The default mode asks before every file edit…243 words2.16Step 12 — Prepare hooks for automated quality checksClaude Code supports hooks — shell commands that run automatically at specific points in Claude's workflow. Unlike CLAUDE.md instructions…293 words2.17Step 13 — Prepare the exact prompt package for Claude CodeBefore moving to Chapter 3, prepare the final set of inputs Claude Code will read.34 words2.18Step 14 — Final pre-scaffolding checklistDo not move to Chapter 3 until all of the following are true:113 words2.19What not to do in this chapterDo not:54 words2.20Deliverable from Chapter 2You should now have:131 words