mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-19 02:17:09 +00:00
* chore(design): export dashboard tokens for design tools
Mockup tools read a design system's tokens.json rather than our CSS, so
designs drifted from the dashboard's Clean theme. The script derives the
tokens from components.css, and CI runs its test so a new color
variable without a usage note fails instead of silently going missing.
* feat(plugin): add npm packages from pi.dev through Pi
Pi packages on pi.dev are npm packages, which Plugins could not add:
it only took local or Git sources, so users had to install them with Pi
and import them. `plugin add npm:<package>` now hands them to
`pi install` for Pi targets and records the binding like an import.
Skillshare can't fetch or review an npm package, and Pi runs its install
scripts, so the preview says so, discover refuses npm sources, and only
targets that run pi itself take them. Pi keeps one entry per package
name, so another version replaces it in place and keeps its extension
filters; Skillshare records the new entry so a reinstall restores them,
and refuses a package another Skillshare package already manages, since
removing one would remove both. Pinned versions are skipped on update
because pi update keeps them.
The dashboard accepts npm sources, a pasted `pi install` command or a
pi.dev address, lists only Pi targets, and the Pi Extensions tab links
to adding a package with that target selected. Pi packages show Pi's
mark in the plugin list.
A blocked change now keeps its own reason when the Agent's CLI is also
missing, and the message key always matches the message the CLI prints.
* fix(plugin): keep npm package names and accept pi by path
The default name of an npm package went through the file-path rule, which
cut its last dot segment as an extension: npm:foo.bar was recorded as foo,
and adding npm:foo.bar@1.2.3 later derived foo.bar and was refused as
another package managing the same Pi entry. npm names are now taken from
the package spec.
A Pi account whose CLI is an absolute path to pi was treated as running
another executable, so it could not take npm packages. It now uses the
same path- and platform-aware check as the Pi Extensions tab.
* docs(wiki): add a pull-requests topic for Codex review rounds
Handling Codex's review was only known from practice: confirm each
finding, fix it with a failing test first, reply in its thread, ask for
another review, and follow up until it answers. Writing it down keeps
agents from resolving threads, amending pushed commits, or stopping at
the 👀 that only means the review is still running.
* feat(ui): give the Extras AGENTS.md and Memory tabs one layout
The two tabs shared a page but looked like different products: the header
shifted between them, notes sat in a joined box with an icon toolbar, and
agents showed as an icon strip in a side card. Switching tabs felt jarring.
Memory now follows the AGENTS.md layout: a sticky list column with search,
the note's name with Edit and a More actions menu, the same preview box,
and Use with agents as one row per tool under the note. Long notes open
collapsed like shared files do. The AGENTS.md list gains a search box and
the same sticky column. The Memory tab label stays English in every locale,
like AGENTS.md. Docs and screenshots follow the new layout.
* chore(docs): add a script that serves the Memory screenshot homes
The Memory how-to screenshots came from demo homes that were never
recorded, so reshooting them meant rebuilding the data by hand. The script
rebuilds the fresh and the populated home inside the devcontainer, serves
each behind the Vite dev server, and hands the port back to air afterwards.
* fix(plugin): refuse npm sources Pi can't resolve
validNpmSource accepted specs such as npm:foo/bar, npm:foo@ and names
containing "..", which Pi's own parser rejects. They passed preview, and
Apply recorded a pending binding before pi install failed, leaving an
entry every later sync retried. Validate with the same grammar the Pi
settings reader uses, which also covers a scope without a package name.
* fix(ui): show the default name when adding an npm package to Pi
The name field for an npm source was blank, so it looked like a name was
missing. Leaving it empty records the package name without its version or
scope, as the git flow already shows; the field now shows that name as its
placeholder.
5.3 KiB
5.3 KiB
AGENTS.md — skillshare
skillshare is a Go CLI with a React dashboard and a Docusaurus documentation site. It synchronizes skills, agents, extras, MCP servers, and plugins across AI coding tools. This file contains only rules needed for every task; load task-specific details through the context topics below.
Language
- Instruction files, internal documentation, public English documentation, code, identifiers, comments, and commit messages use English.
- Reply to users in their language; default to Traditional Chinese when the user writes Chinese.
README.mdis the public English source. Keep translated READMEs aligned with its existing localization conventions. Preserve history files in their original language.
Always Applies
- Use executable evidence. Verify facts that affect conclusions or implementation against current source, configuration, installed versions, or actual command output. Distinguish facts, assumptions, and uncertainty.
- Preserve user changes and keep scope minimal. Inspect the working tree before editing, then trace relevant definitions, callers, tests, and existing patterns. Never overwrite unrelated changes or perform opportunistic cleanup.
- Keep the docs true. When documentation disagrees with code, verify the code and fix the stale documentation in the same task. Update a topic whenever a change alters behavior it describes. Put completed milestone logs in
wiki/history/and add them to the index. Runpython3 scripts/ai-context.py checkafter documentation changes. The maintenance procedure is in theai-contexttopic. - Run commands in the correct environment. Execute the skillshare CLI, Go builds/tests, UI tooling, and website tooling inside the devcontainer. The host is only for file edits, read-only searches, Git inspection, and the context-router check. Load
testingbefore execution or debugging. - Verify in proportion to risk. Start with the narrowest check that proves the change. Reproduce bugs and add regression tests when practical. Never skip, disable, or weaken validation to obtain a passing result.
- Respect authorization boundaries. Reviews, investigations, and diagnoses are read-only by default. Do not commit, push, publish, deploy, install global tools, or perform destructive or irreversible actions unless explicitly authorized.
- Use Git safely. Never overwrite user changes. When asked to commit, stage only task-owned files and follow repository conventions; otherwise use an English Conventional Commit with a body explaining why.
- Keep helper files in the repository. Put reusable helper scripts in
scripts/<area>/and test runbooks inai_docs/tests/. Do not store persistent task artifacts outside the repository. - Report outcomes precisely. State what changed, why, actual verification results, limitations, and preserved unrelated changes. Explicitly identify checks that were not run.
Hard Limits
- Never run
ss,skillshare,go test,make test, or frontend package scripts on the host. - Never expose, hardcode, or commit secrets, tokens, credentials, or private user-path contents.
- Never bypass audits, hooks, tests, trust prompts, or native client confirmation.
- Never change permissions, delete persistent data, rewrite Git history, commit, tag, push, or release without explicit authorization.
- Resolve and confirm the exact target before a destructive action. Never recursively delete a workspace root, home directory, or unresolved broad path.
Load Context Per Task
python3 scripts/ai-context.py list # list topics and selection guidance
python3 scripts/ai-context.py <topic> # print only that topic's sources
python3 scripts/ai-context.py check # validate paths, headings, orphans, and byte budgets
The router runs on the host and needs only Python 3.8+. On Windows, use py or python when python3 is not available.
| Topic | Use when |
|---|---|
architecture |
Tracing repository structure, data flow, or CLI/Web API boundaries |
cli-development |
Adding or changing Go CLI commands, flags, handlers, TUIs, or mutating behavior |
testing |
Building, testing, reproducing bugs, using the devcontainer/ssenv, or running E2E runbooks |
frontend |
Changing React, CSS, layout, or visual behavior in ui/ or website/ |
documentation |
Updating README files, website docs, command flags, translations, or the built-in skill |
release |
Writing changelogs or release notes, bumping versions, tagging, or releasing |
audit |
Read-only consistency checks for flags, docs, tests, targets, handler splits, oplog, or Web API |
pull-requests |
Opening a pull request or handling its review comments, including Codex review |
ai-context |
Adding, moving, or splitting wiki topics, or fixing router checks |
Pick the single closest topic by default. Load a second only when a task genuinely crosses two seams. If no topic fits, read wiki/README.md.
To add a topic:
- Put its content in
wiki/. - Map it in
wiki/ai-context.json. - Add it to this table and
wiki/README.md. - Run
check.
Split an over-budget topic instead of raising its cap. Skills are workflow adapters that load topics; they are not the sole source of repository rules.
Verification
python3 scripts/ai-context.py check
# Code changes: run inside the devcontainer after loading `testing`
make check