Astra Learning Hub · 100 Practical Learning Points

Project brief

1. Theory — what and why

Define audience, user goal and three required page actions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write a one-page brief with acceptance criteria.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Brief has audience, scope and measurable success.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Project brief” was completed correctly? Compare your answer with the verification requirement above.

Information architecture

1. Theory — what and why

Group content into Home, Services, Work and Contact. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draw a navigation tree and label each page.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Every destination has one unambiguous label.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Information architecture” was completed correctly? Compare your answer with the verification requirement above.

Semantic HTML

1. Theory — what and why

Use header, nav, main, section and footer by meaning. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build an index.html skeleton using semantic tags.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

<header><nav aria-label="Main">...</nav></header>
<main><h1>Our Services</h1><section aria-labelledby="services">...</section></main>
<footer>Contact us</footer>

3. Expected output / verification

Inspect DOM and confirm landmarks.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Semantic HTML” was completed correctly? Compare your answer with the verification requirement above.

Accessible headings

1. Theory — what and why

Use one H1 and nested H2/H3 by hierarchy. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Outline headings before styling and test screen-reader order.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Heading sequence reads logically.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Accessible headings” was completed correctly? Compare your answer with the verification requirement above.

Navigation links

1. Theory — what and why

Use real href targets and meaningful link text. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create anchors and verify each destination exists.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No dead or empty links.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Navigation links” was completed correctly? Compare your answer with the verification requirement above.

Responsive viewport

1. Theory — what and why

Configure viewport and fluid widths. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Add viewport meta and test at 360px and desktop.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No horizontal scrolling.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Responsive viewport” was completed correctly? Compare your answer with the verification requirement above.

CSS variables

1. Theory — what and why

Centralize brand colors and spacing tokens. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Define :root custom properties and reuse in cards.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Changing one token updates all cards.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “CSS variables” was completed correctly? Compare your answer with the verification requirement above.

Flexbox navigation

1. Theory — what and why

Align logo, links and actions without absolute offsets. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create flex container with gap and wrap.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Navigation remains usable on mobile.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Flexbox navigation” was completed correctly? Compare your answer with the verification requirement above.

CSS Grid cards

1. Theory — what and why

Build responsive service cards. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use repeat(auto-fit,minmax(...)) and test widths.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

.cards { display:grid; grid-template-columns:repeat(auto-fit,minmax(min(100%,240px),1fr)); gap:1rem; }

3. Expected output / verification

Cards reflow without clipping.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “CSS Grid cards” was completed correctly? Compare your answer with the verification requirement above.

Typography scale

1. Theory — what and why

Use readable line-height and fluid font sizing. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Apply clamp() to H1 and set body line-height.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Headings fit 320px screens.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Typography scale” was completed correctly? Compare your answer with the verification requirement above.

Form labels

1. Theory — what and why

Associate each field with a label. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create form with for/id pairs and required flags.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Clicking label focuses its field.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Form labels” was completed correctly? Compare your answer with the verification requirement above.

Client-side validation

1. Theory — what and why

Reject malformed entries without hiding errors. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use constraint validation and display a clear error message.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Invalid data is blocked and explained.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Client-side validation” was completed correctly? Compare your answer with the verification requirement above.

DOM rendering

1. Theory — what and why

Render an array into cards safely. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build cards using createElement and textContent.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Three items appear without raw HTML injection.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “DOM rendering” was completed correctly? Compare your answer with the verification requirement above.

Search filtering

1. Theory — what and why

Filter cards by normalized query. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Connect input event to a case-insensitive filter.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

const q = input.value.trim().toLowerCase();
cards.forEach(card => { card.hidden = !card.textContent.toLowerCase().includes(q); });

3. Expected output / verification

Search results update immediately.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Search filtering” was completed correctly? Compare your answer with the verification requirement above.

Local persistence

1. Theory — what and why

Store user-selected display preferences. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Save theme in localStorage with try/catch.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Theme survives reload when storage allowed.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Local persistence” was completed correctly? Compare your answer with the verification requirement above.

Async fetch

1. Theory — what and why

Load JSON and handle network failure. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Fetch a local JSON file using try/catch and response.ok.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

try { const r=await fetch("./items.json"); if(!r.ok) throw new Error(`HTTP ${r.status}`); const data=await r.json(); render(data); } catch(e) { showError(e.message); }

3. Expected output / verification

Success renders items; failure shows retry.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Async fetch” was completed correctly? Compare your answer with the verification requirement above.

Keyboard access

1. Theory — what and why

Make controls usable without mouse. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Tab through interface and add visible :focus-visible styles.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Focus is always visible.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Keyboard access” was completed correctly? Compare your answer with the verification requirement above.

Performance audit

1. Theory — what and why

Measure image sizes and loading cost. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use browser Network tab and lazy-load noncritical images.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Page transfers less data on repeat tests.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Performance audit” was completed correctly? Compare your answer with the verification requirement above.

SEO essentials

1. Theory — what and why

Write unique title, description and canonical URL when hosted. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Inspect page source and preview search snippet.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Metadata describes actual page content.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “SEO essentials” was completed correctly? Compare your answer with the verification requirement above.

Deployment QA

1. Theory — what and why

Test pages, forms, paths and rollback. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Deploy to staging and run a 10-case checklist.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No 404s; deployment can be reverted.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Deployment QA” was completed correctly? Compare your answer with the verification requirement above.

App requirements

1. Theory — what and why

Identify target users, offline needs and permissions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write user stories and acceptance checks.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Scope is testable before coding.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “App requirements” was completed correctly? Compare your answer with the verification requirement above.

Flutter environment

1. Theory — what and why

Understand Flutter SDK, Android SDK and emulator requirements. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Install official SDKs and run flutter doctor.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Doctor shows actionable diagnostics.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Flutter environment” was completed correctly? Compare your answer with the verification requirement above.

Project creation

1. Theory — what and why

Use stable package identity and directory structure. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run flutter create learning_demo and inspect lib/main.dart.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

flutter create learning_demo
cd learning_demo
flutter run

3. Expected output / verification

App runs with default counter screen.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Project creation” was completed correctly? Compare your answer with the verification requirement above.

Widget tree

1. Theory — what and why

Understand composition and build context. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Replace counter with MaterialApp and Scaffold.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Screen displays app bar and content.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Widget tree” was completed correctly? Compare your answer with the verification requirement above.

Theme system

1. Theory — what and why

Use consistent colors, typography and spacing. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create ThemeData and apply it to MaterialApp.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

All screens inherit theme.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Theme system” was completed correctly? Compare your answer with the verification requirement above.

Navigation

1. Theory — what and why

Use named or declarative routes consistently. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create Home and Details screens with Navigator.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Back returns to previous screen.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Navigation” was completed correctly? Compare your answer with the verification requirement above.

Form inputs

1. Theory — what and why

Capture validated name and email. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use TextFormField and GlobalKey<FormState>.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Invalid entries show clear errors.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Form inputs” was completed correctly? Compare your answer with the verification requirement above.

State management

1. Theory — what and why

Separate data from widget rendering. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use ChangeNotifier or ValueNotifier for a counter.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

State updates without manual refresh.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “State management” was completed correctly? Compare your answer with the verification requirement above.

Lists and keys

1. Theory — what and why

Render stable dynamic records. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build ListView.builder with stable item keys.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Records display and update correctly.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Lists and keys” was completed correctly? Compare your answer with the verification requirement above.

Local data

1. Theory — what and why

Persist small non-sensitive preferences. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use shared_preferences and load on startup.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Preference remains after app restart.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Local data” was completed correctly? Compare your answer with the verification requirement above.

SQLite concepts

1. Theory — what and why

Store structured offline records safely. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create a local schema and CRUD repository.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Records persist and can be queried.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “SQLite concepts” was completed correctly? Compare your answer with the verification requirement above.

Async lifecycle

1. Theory — what and why

Avoid setState after widget disposal. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Check mounted after await before updating UI.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No lifecycle exceptions on navigation.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Async lifecycle” was completed correctly? Compare your answer with the verification requirement above.

HTTP client

1. Theory — what and why

Handle API status, timeout and invalid JSON. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Call a test endpoint and show loading/error/success.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Failures are visible and recoverable.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “HTTP client” was completed correctly? Compare your answer with the verification requirement above.

Permissions

1. Theory — what and why

Request only necessary Android permissions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Audit manifest and explain runtime requests.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No unrelated permissions.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Permissions” was completed correctly? Compare your answer with the verification requirement above.

Accessibility

1. Theory — what and why

Support text scaling and semantic labels. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Test large fonts and screen reader labels.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Controls remain readable and reachable.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Accessibility” was completed correctly? Compare your answer with the verification requirement above.

App icons

1. Theory — what and why

Prepare adaptive icon foreground/background. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Generate icon resources and inspect launcher.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Icon is not cropped on devices.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “App icons” was completed correctly? Compare your answer with the verification requirement above.

Release signing

1. Theory — what and why

Understand keystore protection and signing. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create a test keystore and configure release signing locally.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Signed build uses private key safely.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Release signing” was completed correctly? Compare your answer with the verification requirement above.

APK vs AAB

1. Theory — what and why

Choose artifact for testing or Play distribution. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run flutter build apk and flutter build appbundle.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

flutter build apk --release
flutter build appbundle --release

3. Expected output / verification

Outputs exist at documented build paths.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “APK vs AAB” was completed correctly? Compare your answer with the verification requirement above.

Device QA

1. Theory — what and why

Test install, rotate, offline and back navigation. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run a physical-device test matrix.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Issues are logged with reproduction steps.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Device QA” was completed correctly? Compare your answer with the verification requirement above.

Publishing readiness

1. Theory — what and why

Review privacy, data safety and store listing. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Prepare listing, screenshots and policy checklist.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Release package passes pre-submission review.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Publishing readiness” was completed correctly? Compare your answer with the verification requirement above.

Architecture choice

1. Theory — what and why

Decide when to use Firebase vs custom backend. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draw data flow and trust boundaries.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Diagram distinguishes client and server.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Architecture choice” was completed correctly? Compare your answer with the verification requirement above.

Firebase project

1. Theory — what and why

Choose region, billing and environment naming. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create separate development project in Firebase Console.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Dev project is isolated.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Firebase project” was completed correctly? Compare your answer with the verification requirement above.

Android registration

1. Theory — what and why

Match Android applicationId exactly. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Register app and place google-services.json correctly.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Firebase initialization succeeds.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Android registration” was completed correctly? Compare your answer with the verification requirement above.

SHA fingerprints

1. Theory — what and why

Know when SHA-1/SHA-256 are required. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Generate signing certificate fingerprints for relevant integrations.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Registered fingerprints match build variant.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “SHA fingerprints” was completed correctly? Compare your answer with the verification requirement above.

Auth providers

1. Theory — what and why

Enable only intended sign-in methods. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Enable email/password in Firebase Console.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Unsupported sign-ins remain disabled.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Auth providers” was completed correctly? Compare your answer with the verification requirement above.

Signup validation

1. Theory — what and why

Validate fields and show auth errors safely. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create test user with Firebase Auth SDK.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

User appears in Authentication console.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Signup validation” was completed correctly? Compare your answer with the verification requirement above.

Session handling

1. Theory — what and why

Observe auth state and route securely. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Listen to authStateChanges and show protected screen.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Logged-out user cannot access protected UI.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Session handling” was completed correctly? Compare your answer with the verification requirement above.

Password reset

1. Theory — what and why

Use provider-supported reset workflow. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Trigger reset email in test account.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Reset link reaches test mailbox.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Password reset” was completed correctly? Compare your answer with the verification requirement above.

Firestore modeling

1. Theory — what and why

Plan documents, IDs and query patterns. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Design users/{uid} and tasks/{taskId} schema.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Fields support required queries.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Firestore modeling” was completed correctly? Compare your answer with the verification requirement above.

Rules basics

1. Theory — what and why

Default deny and least privilege. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write rules that require request.auth != null.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

match /users/{userId} { allow read, write: if request.auth != null && request.auth.uid == userId; }

3. Expected output / verification

Unauthenticated reads fail in emulator.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Rules basics” was completed correctly? Compare your answer with the verification requirement above.

Owner rules

1. Theory — what and why

Restrict per-user document access. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Check request.auth.uid equals document owner.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Other users cannot read/write.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Owner rules” was completed correctly? Compare your answer with the verification requirement above.

Rules tests

1. Theory — what and why

Test both allowed and denied cases. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write emulator tests for owner and outsider.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Both expected allow and deny tests pass.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Rules tests” was completed correctly? Compare your answer with the verification requirement above.

Indexes

1. Theory — what and why

Understand composite query indexes. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run a filtered and sorted query and inspect index error.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Required index is created intentionally.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Indexes” was completed correctly? Compare your answer with the verification requirement above.

Transactions

1. Theory — what and why

Avoid race conditions on shared counters. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use runTransaction for atomic update.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Concurrent updates preserve count.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Transactions” was completed correctly? Compare your answer with the verification requirement above.

Cloud Functions

1. Theory — what and why

Keep privileged logic server-side. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create callable function with auth verification.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Anonymous call rejected.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Cloud Functions” was completed correctly? Compare your answer with the verification requirement above.

Secrets

1. Theory — what and why

Never put admin keys in client code. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use secret manager or environment configuration.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No secrets committed to repository.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Secrets” was completed correctly? Compare your answer with the verification requirement above.

REST API

1. Theory — what and why

Validate JSON, status codes and rate limits. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Call endpoint with explicit timeout and schema checks.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Invalid response handled gracefully.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “REST API” was completed correctly? Compare your answer with the verification requirement above.

Webhook verification

1. Theory — what and why

Verify origin and prevent replay. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Validate signed payload and timestamp on server.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Tampered payload rejected.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Webhook verification” was completed correctly? Compare your answer with the verification requirement above.

Monitoring

1. Theory — what and why

Record actionable errors without sensitive data. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Add structured error logging and alerts.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Failure can be diagnosed without leaked tokens.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Monitoring” was completed correctly? Compare your answer with the verification requirement above.

Production review

1. Theory — what and why

Audit billing, rules, quotas and backups. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run security and restore checklist.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Release has documented rollback and owner.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Production review” was completed correctly? Compare your answer with the verification requirement above.

Audience research

1. Theory — what and why

Define audience segments and problems. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Interview or simulate five user questions.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Documented pain points guide content.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Audience research” was completed correctly? Compare your answer with the verification requirement above.

Keyword intent

1. Theory — what and why

Distinguish informational and transactional intent. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Classify 20 queries by intent.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Each query maps to suitable content.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Keyword intent” was completed correctly? Compare your answer with the verification requirement above.

Content cluster

1. Theory — what and why

Build pillar page and supporting articles. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draft a topic map for one niche.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No duplicate pages target same intent.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Content cluster” was completed correctly? Compare your answer with the verification requirement above.

Search snippet

1. Theory — what and why

Write accurate titles and descriptions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create two title/description alternatives.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Snippets match page value.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Search snippet” was completed correctly? Compare your answer with the verification requirement above.

Technical crawl

1. Theory — what and why

Understand robots.txt, sitemaps and canonical tags. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Inspect site with Search Console URL inspection.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Indexability issues are identified.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Technical crawl” was completed correctly? Compare your answer with the verification requirement above.

Core Web Vitals

1. Theory — what and why

Understand LCP, INP and CLS. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Run Lighthouse and log measured values.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Performance issues have priorities.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Core Web Vitals” was completed correctly? Compare your answer with the verification requirement above.

Structured data

1. Theory — what and why

Use valid schema only for real content. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Add appropriate JSON-LD and validate.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Rich result test has no critical errors.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Structured data” was completed correctly? Compare your answer with the verification requirement above.

Internal links

1. Theory — what and why

Create descriptive links without loops. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Map ten relevant content connections.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Each link serves user navigation.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Internal links” was completed correctly? Compare your answer with the verification requirement above.

Analytics events

1. Theory — what and why

Define meaningful user actions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write event measurement plan for signup/download.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Events have names and parameters.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Analytics events” was completed correctly? Compare your answer with the verification requirement above.

Consent and privacy

1. Theory — what and why

Handle cookies and user choices responsibly. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Document collection purpose and consent needs.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Tracking aligns with disclosed choices.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Consent and privacy” was completed correctly? Compare your answer with the verification requirement above.

Conversion funnel

1. Theory — what and why

Map discovery to action and retention. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draw landing→engage→convert stages.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Drop-off points are measurable.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Conversion funnel” was completed correctly? Compare your answer with the verification requirement above.

Landing page

1. Theory — what and why

Use clear value proposition and CTA. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build two headline variants with one CTA.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Page communicates benefit quickly.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Landing page” was completed correctly? Compare your answer with the verification requirement above.

Google Ads structure

1. Theory — what and why

Separate campaigns by objective and intent. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draft campaign/ad-group/keyword sheet.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Ad groups have coherent themes.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Google Ads structure” was completed correctly? Compare your answer with the verification requirement above.

Negative keywords

1. Theory — what and why

Avoid irrelevant ad traffic. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create negative keyword review list.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Wasted-query risks documented.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Negative keywords” was completed correctly? Compare your answer with the verification requirement above.

Meta Ads creative

1. Theory — what and why

Match message to audience and format. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draft three ad creatives and hypotheses.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Each creative tests a distinct angle.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Meta Ads creative” was completed correctly? Compare your answer with the verification requirement above.

UTM tracking

1. Theory — what and why

Use consistent source, medium and campaign. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build tagged links and verify analytics parsing.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

https://example.com/course?utm_source=instagram&utm_medium=social&utm_campaign=course_launch

3. Expected output / verification

Visits attributed consistently.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “UTM tracking” was completed correctly? Compare your answer with the verification requirement above.

Affiliate disclosures

1. Theory — what and why

Make commercial relationships transparent. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Place disclosure near affiliate recommendation.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Disclosure is conspicuous.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Affiliate disclosures” was completed correctly? Compare your answer with the verification requirement above.

Pricing services

1. Theory — what and why

Estimate time, scope and revision costs. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Prepare fixed-price quote with assumptions.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Quote includes deliverables and exclusions.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Pricing services” was completed correctly? Compare your answer with the verification requirement above.

Client proposals

1. Theory — what and why

Translate needs into milestones and acceptance. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draft proposal and payment milestones.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Scope changes require approval.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Client proposals” was completed correctly? Compare your answer with the verification requirement above.

Optimization report

1. Theory — what and why

Prioritize actions by evidence, not vanity metrics. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create weekly KPI table and next-action log.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Recommendations trace to measurements.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Optimization report” was completed correctly? Compare your answer with the verification requirement above.

Creative brief

1. Theory — what and why

Specify audience, channel, tone and deliverables. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write brief for a digital learning campaign.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Brief sets measurable design requirements.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Creative brief” was completed correctly? Compare your answer with the verification requirement above.

Brand positioning

1. Theory — what and why

Differentiate audience promise from competitors. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Draft positioning statement and three values.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Brand message is consistent.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Brand positioning” was completed correctly? Compare your answer with the verification requirement above.

Logo concepts

1. Theory — what and why

Design scalable symbol and wordmark options. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Sketch three monochrome logo directions.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Each is recognizable at small size.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Logo concepts” was completed correctly? Compare your answer with the verification requirement above.

Vector workflow

1. Theory — what and why

Use SVG paths and clean typography. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build a simple vector logo in a vector editor.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Logo stays sharp when resized.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Vector workflow” was completed correctly? Compare your answer with the verification requirement above.

Color accessibility

1. Theory — what and why

Choose contrast-safe palette. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Check text/background contrast ratios.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Body text meets WCAG contrast target.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Color accessibility” was completed correctly? Compare your answer with the verification requirement above.

Type hierarchy

1. Theory — what and why

Create readable heading/body scales. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Define 3 text sizes and weights.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Hierarchy clear on mobile.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Type hierarchy” was completed correctly? Compare your answer with the verification requirement above.

Brand guidelines

1. Theory — what and why

Document spacing, color and misuse rules. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create one-page brand sheet.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Future assets follow same rules.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Brand guidelines” was completed correctly? Compare your answer with the verification requirement above.

Thumbnail research

1. Theory — what and why

Study legibility at small screen sizes. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Compare five thumbnails at 160px width.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Core message remains readable.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Thumbnail research” was completed correctly? Compare your answer with the verification requirement above.

Thumbnail composition

1. Theory — what and why

Use one focal point and limited text. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Build 1280×720 thumbnail mockup.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Subject and headline remain distinct.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Thumbnail composition” was completed correctly? Compare your answer with the verification requirement above.

Poster layouts

1. Theory — what and why

Balance whitespace and visual hierarchy. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create square and vertical poster variants.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Both have correct safe margins.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Poster layouts” was completed correctly? Compare your answer with the verification requirement above.

AI image prompts

1. Theory — what and why

Describe subject, style, framing and exclusions. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write three original prompts and compare outputs.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Selected image matches brief.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “AI image prompts” was completed correctly? Compare your answer with the verification requirement above.

AI output review

1. Theory — what and why

Check artifacts, rights and factual accuracy. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Use quality checklist before publishing.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Unverified claims removed.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “AI output review” was completed correctly? Compare your answer with the verification requirement above.

Video outline

1. Theory — what and why

Structure hook, explanation, demo and recap. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Write a 5-minute tutorial outline.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Every segment has purpose.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Video outline” was completed correctly? Compare your answer with the verification requirement above.

Storyboard

1. Theory — what and why

Map visuals to spoken lines and timing. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create shot list with timecodes.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No scene lacks visual purpose.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Storyboard” was completed correctly? Compare your answer with the verification requirement above.

Screen recording

1. Theory — what and why

Capture readable cursor and UI. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Record 1080p demo with large UI scaling.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Text is readable on phone.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Screen recording” was completed correctly? Compare your answer with the verification requirement above.

Male narration

1. Theory — what and why

Write natural conversational Telugu/English/Hindi scripts. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Record short test and inspect pauses/pronunciation.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Voice is intelligible without robotic gaps.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Male narration” was completed correctly? Compare your answer with the verification requirement above.

Subtitle timing

1. Theory — what and why

Sync captions to speech with short lines. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create SRT and verify playback.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

Example / command

1
00:00:01,000 --> 00:00:03,000
Welcome to the lesson.

3. Expected output / verification

Captions follow narration accurately.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Subtitle timing” was completed correctly? Compare your answer with the verification requirement above.

Editing workflow

1. Theory — what and why

Cut mistakes and balance audio levels. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Assemble screen recording, narration and music.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Dialogue is clear and not masked.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Editing workflow” was completed correctly? Compare your answer with the verification requirement above.

Export presets

1. Theory — what and why

Choose 16:9, 9:16 and bitrate appropriately. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Export test clips and inspect on mobile.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

No important text is cropped.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Export presets” was completed correctly? Compare your answer with the verification requirement above.

Publishing & reuse

1. Theory — what and why

Package title, description, thumbnail and source. This skill matters because it provides a verifiable foundation for the next stage of the project.

2. Step-by-step guided practice

1. Prepare: Open the relevant project or editor and identify the files, configuration or campaign affected by this point.
2. Perform: Create release checklist and editable source archive.
3. Inspect: Compare the result against the expected behavior below; capture a screenshot or log for evidence.
4. Improve: Change one input or setting, repeat the test, and record how the result changes.

3. Expected output / verification

Content can be updated without rebuilding from scratch.

4. Troubleshooting

If the result differs, check the exact input, file path, access permissions, tool version and error message. Reproduce with the smallest test case; undo the last change before retrying.

5. Independent practice

Repeat this task using a different realistic project, explain why each decision was made, and submit the final artifact plus a short verification note.

6. Knowledge check

What evidence proves that “Publishing & reuse” was completed correctly? Compare your answer with the verification requirement above.