Skip to content
Skills Library
Programming · Learning & explanation

protowiki-getting-started

/protowiki-getting-started

Orientation for the ProtoWiki repo — what it is, the Vite + Vue 3 + Codex + GitHub Pages stack, where code lives, where skills live, and the first thing to do. Use when first opening this repo, when asked "what is ProtoWiki" or "how does this repo work", or when an agent needs a high-level map before doing anything else.

Repository
protowiki ↗
Licence
LGPL
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

LGPL, otwarta.

What it does and when to use it

Orientation for the ProtoWiki repo — what it is, the Vite + Vue 3 + Codex + GitHub Pages stack, where code lives, where skills live, and the first thing to do. Use when first opening this repo, when asked "what is ProtoWiki" or "how does this repo work", or when an agent needs a high-level map before doing anything else.

Triggers from the description

what is ProtoWikihow does this repo work
Original author description

Orientation for the ProtoWiki repo — what it is, the Vite + Vue 3 + Codex + GitHub Pages stack, where code lives, where skills live, and the first thing to do. Use when first opening this repo, when asked "what is ProtoWiki" or "how does this repo work", or when an agent needs a high-level map before doing anything else.

How it works

  1. What this repo is
  2. Tech stack
  3. Where things live
  4. What to do next
  5. Local dev
Original SKILL.md headings · 94 lines, 611 words
SKILL.md preview
---
name: protowiki-getting-started
description: Orientation for the ProtoWiki repo — what it is, the Vite + Vue 3 + Codex + GitHub Pages stack, where code lives, where skills live, and the first thing to do. Use when first opening this repo, when asked "what is ProtoWiki" or "how does this repo work", or when an agent needs a high-level map before doing anything else.
---

# ProtoWiki — getting started

## What this repo is

ProtoWiki is a prototyping playground for Wikimedia features. It is **not**
a CMS, not a real wiki, not a deployed product. It exists so that designers,
PMs, and engineers can stand up a realistic-looking Wikipedia / MediaWiki
prototype in minutes, hand it to a researcher, and link it from a Phabricator
ticket — using the **same design system, the same fonts, and (optionally)
the same real data** as production.

Realism is the goal. The repo bundles:

- The Wikimedia [Codex design system](https://doc.wikimedia.org/codex/) (Vue 3
  components, CSS tokens, icons) so prototypes look right.
- Data utilities that talk to the live Wikipedia REST and Action APIs.
- Single-concern layout wrappers that paint each Wikipedia surface (chrome,
  article column, special-page shell, plain canvas) and compose by nesting —
  for the **website** and for the **iOS / Android apps**.
- A skills system under `.agents/skills/` that documents every part of
  the repo for both humans and AI coding agents.

For the full component catalogue, see
[`protowiki-components`](../protowiki-components/SKILL.md).

## Tech stack

- **Vite** + **Vue 3** (Composition API, `<script setup>`)
- **TypeScript**, non-strict (`strict: false`, `allowJs: true`) — optional
  for prototype authors; editors get autocomplete without build errors
- **`unplugin-vue-router`** — file-based routing under `src/prototypes/`
- **`@wikimedia/codex`** + `@wikimedia/codex-design-tokens` +
  `@wikimedia/codex-icons`
- Plain CSS (no preprocessor)
- **Prettier** + **ESLint**
- **GitHub Pages** for hosting (no server needed)

## Where things live

```
protowiki/
├── src/
│   ├── main.ts             ← Vue mount + boot-time skin/theme setup
│   ├── App.vue             ← thin shell (RouterView)
│   ├── prototypes/         ← prototypes (each folder = one route)
│   │   ├── index.vue       ← home / gallery (auto-lists prototypes)
│   │   ├── template-chrome/index.vue
│   │   ├── template-dashboard/index.vue
│   │   └── template-homepage/index.vue
│   ├── components/         ← shipped components (wrappers, primitives, article, dashboard)
│   ├── composables/        ← useSkin / useTheme (read-only hooks)
│   ├── lib/                ← theming logic, helpers
│   └── styles/             ← global.css, wiki-skins/, dark.css
├── .agents/skills/         ← skills for both humans and agents (see below)
├── AGENTS.md               ← thin index pointing at the skills
└── README.md               ← human-friendly intro pointing at the same skills
```

There is **no** `.cursor/rules/`, **no** parallel `resources/` folder, **no**
`CLAUDE.md`. All non-code material is a skill. Skills are markdown that humans
read and that AI agents auto-discover.

## What to do next

| If you want to… | Read… |
| --- | --- |
| Make a new prototype | [`protowiki-create-prototype`](../protowiki-create-prototype/SKILL.md) |
| Prototype the iOS / Android apps rather than the website | [`protowiki-app-prototyping`](../protowiki-app-prototyping/SKILL.md) |
| Customize home gallery listing | [`protowiki-create-prototype` → `gallery-meta.md`](../protowiki-create-prototype/references/gallery-meta.md) |
| Look up a component (wrappers, article surfaces, search bar…) | [`protowiki-components`](../protowiki-components/SKILL.md) |
| Build an article page (live vs hand-authored) | [`protowiki-components`](../protowiki-components/SKILL.md) — **`ArticleLive`** (default) or **`ArticleCustom`**; **`template-article/`**, **`example-custom-article/`** |
| Use a Codex component, token, or icon | [`codex-usage`](../codex-usage/SKILL.md) |
| Fetch real data from Wikipedia | [`wiki-apis`](../wiki-apis/SKILL.md) |
| Snapshot article HTML + skin CSS into the repo (fixtures; copy markup into **`ArticleCustom`**) | [`protowiki-snapshot-data`](../protowiki-snapshot-data/SKILL.md) |
| Prototype VisualEditor-style editing (article template, suggestion mode) | [`protowiki-components` → `editors.md`](../protowiki-components/references/editors.md) |
| Make light/dark or desktop/mobile previews | [`protowiki-skins`](../protowiki-skins/SKILL.md) + [`protowiki-theme`](../protowiki-theme/SKILL.md) |
| Deploy to GitHub Pages | [`protowiki-deploy`](../protowiki-deploy/SKILL.md) |

## Local dev

```bash
npm install
npm run dev      # http://localhost:5173 — use this for prototyping
```

That's it — there's no registration step for new prototypes. Drop a folder
under `src/prototypes/` and the route is live. Gallery **title** and
**description** must not be AI-generated — ask the author or omit; see
[`protowiki-create-prototype`](../protowiki-create-prototype/SKILL.md). CI runs
`npm run build` when
you push or open a PR; you only need a local build to debug GitHub Pages
issues — see [`protowiki-deploy`](../protowiki-deploy/SKILL.md).

Versions

The database has no other skills named protowiki-getting-started.

Database snapshot: 13.11.2026 · package version d4417e65e52f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100protowiki-deploy
    How to build and deploy ProtoWiki to GitHub Pages — production deploy, PR preview deployments on gh-pages, template-first repo setup, base path (PROTOWIKI_BASE), SPA 404 fallback, and CI workflows. Use when asked to deploy, publish, preview a PR, ship to GitHub Pages, set up a…
  • 100protowiki-update-codex
    How to upgrade ProtoWiki to a new version of the Wikimedia Codex design system — bump the three @wikimedia/codex packages in lockstep, diff the upstream design-codex docs between the old and new release tags, propagate documented changes into the codex-* skills, refresh the…
  • 90markstream-vue2-vite
    Integrate markstream-vue2 into a Vue 2 plus Vite app. Use when Codex needs Vite-friendly worker imports, `?worker` or `?worker&inline` setup for Mermaid or KaTeX, modern CSS ordering, or Vue 2 compatibility in a Vite-based repository.
  • 90vue-vite
    Vue + Vue Router + Vite开发专家助手。当用户需要进行Vue SPA搭建、Vite配置、Vue Router、Pinia或现代前端项目开发时调用。
  • 90vue-vite-typescript
    Vue + Vue Router + Vite开发专家助手。当用户需要进行Vue SPA搭建、Vite配置、Vue Router、Pinia或现代前端项目开发时调用。
  • 100vite-development
    Vite 8.0.10 build tooling — HMR, fast builds, plugins, and optimized production assets. Use when configuring Vite, setting up React/Vue projects with Vite, or optimizing frontend build performance.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.