Contribute to quizzes and AI workflows.

The best public entry points are the quiz hub and the workflow hub. Pick one lane, read its guide, start with one small scoped improvement, and keep the change easy to review.

Quiz hub Workflow hub

Choose a lane

Start where the source of truth already lives.

Quiz content

Quiz lane

Use the quiz hub for new YAML, explanation improvements, references, wording fixes, schema clarifications, and other content-side changes to the learner experience.

Add or improve multiple-choice questions.
Tighten `answer.short_explainer`, deeper rationale, and references.
Fix topic placement, difficulty tagging, and YAML consistency.

Open quiz hub Browse topics Submit a quiz

Workflow content

Workflow lane

Use the workflow hub for skills, rules, flow documentation, smoke-suite coverage, examples, and explanations around deterministic ASIC engineering workflows.

Add or refine skills, rules, and workflow documentation.
Improve examples, structure, and evidence-grounded guidance.
Extend smoke coverage and tighten contributor-facing docs.

Open workflows hub Browse flows Read the guide

Start here

Use one of these scoped starting points for a clean first contribution.

Quiz starter issues

High-signal content and authoring improvements

Expand the clock-gating lane with at least 10 new teaching-quality questions.
Add concrete authoring examples for answer.short_explainer, references, and review metadata.
Strengthen quiz metadata validation for learner-facing required fields.

These are good entry points if you want to improve quiz quality, contributor ergonomics, or source-of-truth validation.

Workflow starter issues

Execution, examples, and flow depth

Add a small execution harness for flows/block-level-rtl-plan.
Add a low-power intent planning skill and ruleset for front-end flows.
Publish an end-to-end example chaining block-level-rtl-plan into block-dv-plan.

These are the best public workflow tickets right now if you want to improve real repo structure instead of polishing around the edges.

How to start

Keep the first contribution small, explicit, and reviewable.

Pick one scoped change

Choose one fix, one new question set, one workflow clarification, or one docs improvement instead of bundling multiple ideas.

Read the repo guide first

Use the repo-specific `CONTRIBUTING.md` so the file format, validation path, and review expectations are clear before you edit.

Open an issue if needed

If you do not see a matching issue, open a short proposal first so the change direction is aligned before you invest heavily.

Strong first contributions

Add 3 to 10 well-sourced quiz questions in one topic lane.
Improve weak explanations or add missing references to existing quizzes.
Clarify one workflow skill, rule, or flow page with a better example.
Expand smoke coverage or tighten contributor-facing docs in the workflows repo.

What helps maintainers review fast

State what changed and why in one paragraph.
Link any issue, source, or technical reference you used.
Keep schema or formatting changes explicit.
Call out how you validated the contribution locally if the repo guide asks for it.