@interf/compiler 0.2.5 → 0.3.1

package/templates/workflow-starters/interface/interf/create/SKILL.md

@@ -1,15 +0,0 @@
----
-{
-  "mode": "extend"
-}
----
-# Interf Create Bias
-
-Turn the user's requested task into a concrete compile plan the later stages can actually execute.
-
-- treat `compile-plan.md` as the primary durable output of create; leave scaffolded `AGENTS.md` alone unless it is materially wrong
-- preserve the exact requested use-case line in `compile-plan.md` instead of leaving the generic workflow placeholder
-- carry named markets, years, metrics, units, comparators, and source families verbatim into the target ledger
-- if the task depends on exact values from reports, PDFs, charts, or tables, require a concrete local extraction path instead of vague raw-reading language
-- keep the interface bounded; do not widen into a general report summary unless a comparator or calibration anchor is genuinely needed
-- for automated runs, emit these canonical status markers verbatim and on their own lines: `STATUS: loaded interface creation contract.`, `STATUS: analyzed knowledge-base.`, `STATUS: wrote compile plan.`

package/templates/workflow-starters/knowledge-base/interf/README.md

@@ -1,13 +0,0 @@
----
-{
-  "mode": "extend"
-}
----
-# Interf Knowledge Base Workflow
-
-Bias this knowledge base toward source-grounded summaries, explicit evidence tiers, and retrieval-ready compile outputs.
-
-- keep summary titles and abstracts conservative and source-grounded
-- preserve evidence tiers, truth modes, and draft-vs-final distinctions
-- compile durable entities, claims, indexes, and navigation that make later interfaces easier to retrieve from
-- prefer structures that help agents prove what they scanned, selected, and excluded before synthesis

package/templates/workflow-starters/knowledge-base/karpathy/README.md

@@ -1,13 +0,0 @@
----
-{
-  "mode": "extend"
-}
----
-# Karpathy Knowledge Base Workflow
-
-Bias this knowledge base toward the source folder -> summaries -> compiled markdown knowledge-base loop.
-
-- keep per-source summaries legible and source-grounded
-- prefer markdown-native knowledge artifacts an agent can browse and file back into the base
-- preserve backlinks and local browseability across the knowledge layer
-- treat the compiled base as a maintained working surface for later questions, not just a one-shot export