一键导入
plexium-user
Operate within a Plexium-powered repository — read wiki before work, update wiki after changes, follow ownership rules, use retrieval
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Operate within a Plexium-powered repository — read wiki before work, update wiki after changes, follow ownership rules, use retrieval
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Develop and contribute to the Plexium codebase — package structure, build commands, test patterns, architecture layers
Use when the user wants to install or verify the Plexium CLI from inside Codex.
Use when the user wants to initialize Plexium, set up the current repository for Codex, verify readiness, or connect Plexium's MCP server in Codex.
Use when the user wants to install Plexium, set up the current repo for Claude Code, verify readiness, or query the Plexium wiki from Claude Code.
Use when the user wants to search or retrieve information from the Plexium wiki in the current repository.
This skill should be used when the user asks to "configure Codex CLI", "edit config.toml", "set up Codex settings", "change the Codex model", "configure approval policy", "set sandbox mode", "add an MCP server to Codex", "create a Codex profile", "configure model providers", "set up OTel for Codex", or mentions Codex CLI configuration, config.toml, or settings. Provides comprehensive configuration reference for OpenAI Codex CLI.
| name | plexium-user |
| description | Operate within a Plexium-powered repository — read wiki before work, update wiki after changes, follow ownership rules, use retrieval |
This repository uses Plexium to maintain a persistent wiki that compounds knowledge across agent sessions. You are expected to read from and contribute to the wiki as part of your workflow.
Every task follows four steps:
Before writing any code, retrieve relevant context:
# Search the wiki for relevant pages
plexium retrieve "<topic>"
# Or with JSON output for structured parsing
plexium retrieve "<topic>" --format json
Also read directly:
.wiki/_index.md — full page listing.wiki/_log.md — recent changes and decisions.wiki/_schema.md — governance rules (read reference/schema-guide.md for details)If the wiki has an MCP server configured, use pageindex_search instead of shelling out.
Do the coding task. No special requirements here.
After changing source code, update the wiki:
For module changes — update or create the corresponding page in .wiki/modules/:
---
title: Module Name
ownership: managed
source-files:
- path/to/changed/file.go
last-updated: 2026-04-06
---
For architectural decisions — create a page in .wiki/decisions/:
---
title: Decision Title
ownership: co-maintained
last-updated: 2026-04-06
---
# Decision Title
## Context
## Decision
## Consequences
Always update _log.md — append a timestamped entry:
- **2026-04-06** — [module-name] Brief description of what changed and why
Trivial change exception: Single-file changes that don't affect architecture only need a _log.md entry.
Before committing:
# Refresh manifest mappings, hashes, and staleness markers
plexium sync
# Check for broken wiki-links, orphan pages, stale mappings
plexium lint --deterministic
# Recompile navigation if you added/removed pages
plexium compile
Check page frontmatter before editing:
ownership value | You can... |
|---|---|
managed | Freely edit — this page is agent-maintained |
human-authored | Do not modify — only humans edit this page |
co-maintained | Append to existing sections, do not rewrite |
When in doubt, check reference/ownership-model.md.
| Task | Command |
|---|---|
| Search wiki | plexium retrieve "<query>" |
| Check health | plexium lint --deterministic |
| Rebuild nav | plexium compile |
| Validate setup | plexium doctor |
| View manifest | Read .plexium/manifest.json |
reference/wiki-links.mdreference/taxonomy.mdreference/schema-guide.mdreference/ownership-model.mdreference/retrieval.md