molecule-ai/molecule-core
35
0
Fork 2
Code Issues 18 Pull Requests 2 Actions 52 Packages Projects Releases Wiki Activity
4b6482bea0
molecule-core/docs
History
Research Lead f922f87a22 chore(eco-watch): 2026-04-15 daily survey — 3 new entries, 3 issues 
New entries:
- vercel-labs/skills: canonical agentskills.io CLI (14.2k ⭐, +153)
- coleam00/Archon: YAML-DAG harness builder for AI coding (18.1k ⭐, +396)
- Claude Code Routines: Anthropic cloud-scheduled agents (611 HN pts)

Issues filed:
- #146 plugins/: align with agentskills.io SKILL.md spec
- #147 workspace_schedules: add GitHub event trigger types
- #148 workspace-template/: workflow.yaml YAML-DAG convention

HEAD at survey time: 229c2ab

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-15 10:14:59 +00:00
..
.vitepress initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
adapters initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
agent-runtime initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
api-protocol docs: sync documentation with 2026-04-13 merges (PRs #1-#8) 2026-04-13 17:46:28 -07:00
architecture initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
assets/branding chore: replace brand icon and add HANDOFF.md 2026-04-13 13:03:40 -07:00
demo initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
development docs: correct stale test counts in PR #9 2026-04-13 17:51:12 -07:00
edit-history docs: sync documentation with 2026-04-15 tick-9 merges (#79, #80) 2026-04-14 16:43:00 -07:00
frontend initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
plugins initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
product initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
research initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
runbooks review: split push steps, runbook for secret rotation, username clarity 2026-04-14 17:09:11 -07:00
.gitignore initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
api-reference.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
architecture.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
ecosystem-research-outcomes.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
ecosystem-watch.md chore(eco-watch): 2026-04-15 daily survey — 3 new entries, 3 issues 2026-04-15 10:14:59 +00:00
index.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
known-issues.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
package-lock.json initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
package.json initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
quickstart.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00
README.md chore: structural cleanup — dead dirs, moves, gitignore 2026-04-13 14:06:52 -07:00
remote-workspaces-readiness.md initial commit — Molecule AI platform 2026-04-13 11:55:37 -07:00

README.md

docs/

This directory serves two purposes:

  1. Markdown content — everything under architecture/, agent-runtime/, api-protocol/, development/, frontend/, plugins/, product/, etc. This is what agents and humans read.
  2. VitePress site — .vitepress/config.ts, package.json, package-lock.json. These drive the rendered documentation site.

Local preview

cd docs
npm install
npm run dev      # preview on http://localhost:5173
npm run build    # static build to docs/.vitepress/dist/

Conventions

  • New top-level docs must be linked from PLAN.md, README.md, and CLAUDE.md — otherwise agents can't find them (see .claude/ memory feedback_cross_reference_docs.md).
  • edit-history/YYYY-MM-DD.md is append-only log of significant changes; don't rewrite history.
  • archive/ holds one-shot analyses and retired docs — kept for context but not maintained.

Why site tooling lives here (not in docs-site/)

VitePress expects its config at <root>/.vitepress/config.ts where <root> is also the content directory. Splitting tooling into a sibling docs-site/ would require a non-trivial srcDir shim and break relative links in .vitepress/config.ts. Keeping both together is the pragmatic choice; this README is the tradeoff ledger.