Open
Labels
enhancementNew feature or requestNew feature or request
Description
Summary
Give new users a guided path from "installed sctx and the Claude Code plugin" to "a configured space validating real content", without having to write config by hand first.
User journey
- Someone is working on a project that already contains somewhat structured markdown: typed frontmatter, a knowledge wiki, an Open Knowledge Format bundle (Bundle an Open Knowledge Format (OKF) schema #143), and so on.
- They discover structured-context and install the CLI and the Claude Code plugin.
- An onboarding skill or command (for example
/init-space) scans the project for space-like content:- directories of markdown with consistent frontmatter keys or
typevalues; - OKF bundles (a root
index.mdwithokf_version); - matches against bundled schemas.
- directories of markdown with consistent frontmatter keys or
- It proposes candidate spaces, with a suggested schema, path and type inference settings, and writes the config the user accepts.
- It runs a first validation and summarises the results, so the user sees the size of the gap before anything enforces it.
Staged enablement
Existing content may have many violations. Onboarding should not leave the user with hooks reacting to all of it straight away.
- A per-space or per-project setting that keeps the plugin's automatic hooks off (or report-only) until the user opts in, with
/validate-spaceavailable for manual checks in the meantime. - Hooks already compare against a whole-space baseline (Hooks: whole-space validation baseline at prompt submit, compared at Stop #127), so only new issues are reported, but the first run and noisy spaces still deserve an explicit "not yet" mode.
- Could tie into configurable severity (Allow config overrides of validation severity #92) and parsing strictness (Space config option to control parsing strictness for untyped files #80).
Open questions
- Skill, slash command, or a CLI command (
sctx init) that the skill wraps? A CLI command would also serve non-Claude users. - Where config is written: project-local
config.json, user config, or ask. - How far detection should go: suggest a bundled schema only, or draft a local schema from observed frontmatter.
Related: #89 (skill initialisation), #76 (validation anywhere), #80, #92
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Activity
mindsocket commentedon Oct 22, 2026
Scope extension: from discovery to inferring a schema and importing content
#145 covers discovering space-like markdown and proposing a configuration. Two parts of the same journey are not covered yet, and the open question about drafting a local schema from observed frontmatter is the start of the first one.
1. Infer a schema from existing content. Profile a directory (frontmatter key frequencies, folder-to-type candidates, heading shapes, link patterns), propose a draft schema or the closest bundled one, then check the proposal against the content. Violations from the first validation should feed the next proposal. #117 is the consumer side of that loop.
2. Bring in content that isn't markdown yet. Pull from another system (a wiki, an issue tracker, documents), map fields onto the target schema, emit nodes, then validate.
Approach, skills first.
Open questions
sctx initneeded, or does the skill do everything using existing commands?Related: #117, #38, #37, #89
mindsocket commentedon Oct 26, 2026
Phase 1 is in draft PR #175:
.sctx.jsondiscovery,sctx spaces add, error codes insctx spaces --json, aSessionStartpreflight, and asetup-spaceskill.Decided along the way:
includeSpacesFromis the way to combine configs.--config <folder>/.sctx.jsonor--global); there is no default to the working folder.Later phases:
The Obsidian plugin side is on a separate branch of obsidian-structured-context and needs this released first.