Pending
Bundle OKF 0.2 · 14 conceitos · vvanagas/learn_vue
Open source Repository Open in the app JSON README (API)
About
# Pending
Open work for the `learn_vue` course and the rulesets it depends on. An
[OKF](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md)
bundle: one concept per item, `type: Pending`, frontmatter carrying `state`,
`trigger` and `owner` as producer extensions.
**Nothing here blocks a lesson.** Each item names the condition that fires it, so
the list can be ignored safely until reality arrives. `history.txt` records what
ran; this records what has not run yet and when it would matter.
Numbers are creation order and permanent — they get cited from commit messages,
so they never renumber. Priority is not the number. Closing an item means setting
`state: done` and naming the commit that closed it, never deleting the file.
## Provenance — the `evidence:` field
Every item carries one class for its **load-bearing claim** — the claim that
decides whether the item still matters — plus the date it was assigned and a
one-line basis:
```yaml
evidence: { class: D
Details
- Kind
- OKF bundles
- Topic
- Version control
- Publisher
- vvanagas
- Origin
- okf_github
- Category
- dados
- Version
- 0.2
- Last push
- 2026-07-31T19:12:19Z
- Repository state
- ativo
- Language
- HTML
- Added
- 2026-09-09 19:04:11
- Updated
- 2026-09-09 19:04:11
- Origin id
vvanagas/learn_vue:pending/index.md
README
# learn_vue A stateful teaching workspace for learning Vue 3 + TypeScript over 9 months, driven by the [`teach`](https://github.com/mattpocock/skills/tree/main/skills/productivity/teach) skill from [mattpocock/skills](https://github.com/mattpocock/skills). This repository is not a Vue project. It is the *course* — the mission, the plan, the vetted sources, the lessons, and the record of what was actually learned. The application itself gets built inside it from Phase 4 onward. ## Start here | File | What it is | |------|------------| | [MISSION.md](./MISSION.md) | Why this is being learned. Everything derives from it. | | [LEARNING-PLAN.md](./LEARNING-PLAN.md) | The 7 phases, hour budgets, and exit criteria. | | [RESOURCES.md](./RESOURCES.md) | Vetted sources. Lessons cite these, never model memory. | | [NOTES.md](./NOTES.md) | Background, environment, standing decisions. | ## Directories - `lessons/` — numbered self-contained HTML lessons, the primary unit of teaching. - `reference/` — compressed cheat sheets, the documents actually revisited. - `learning-records/` — ADR-style records of what was learned and what changed. - `assets/` — shared stylesheet and reusable components across lessons. - `.claude/skills/coding-rules/` — vendored house ruleset (CC BY 4.0), phases in at Phase 6. ## Running a session The `teach` skill must be installed at `~/.claude/skills/teach/`, then: ```bash cd C:\darbas4\learn_vue ``` Open Claude Code in that directory and run `/teach`. The skill treats the current directory as the workspace, so launching from anywhere else scatters lessons into the wrong tree. ## Open item The application to be built is **not yet named** — see the OWED section at the bottom of [MISSION.md](./MISSION.md). The plan holds without it through Phase 3; Phase 4 cannot start until it is chosen. ## Attribution - `teach` skill — [mattpocock/skills](https://github.com/mattpocock/skills), MIT. - `coding-rules` — [vvanagas/coding-rules](https://github.com/vvanagas/coding-rules), CC BY 4.0.