Skip to content

docs: add CLAUDE.md with correct fasten-core paths + fasten-build skill#71

Open
cyberwalk3r wants to merge 3 commits into
mainfrom
docs/claude-md-fasten-core-paths
Open

docs: add CLAUDE.md with correct fasten-core paths + fasten-build skill#71
cyberwalk3r wants to merge 3 commits into
mainfrom
docs/claude-md-fasten-core-paths

Conversation

@cyberwalk3r

Copy link
Copy Markdown
Collaborator

What

Adds the repo-root CLAUDE.md (previously untracked, so no other checkout ever saw it) with correct fasten-core paths, plus a fasten-build starter skill.

Why

The draft file referenced a store-core/ crate that does not exist - every build/test command in it failed verbatim. The Rust core lives at fasten-core/ (lib fasten_core -> libfasten_core.so, header fasten-core/include/fasten_core.h), exactly as CI already uses in fasten-py.yml. Agent/editor tooling reads this file as ground truth, so a wrong copy is worse than none.

Affected SDK / surface

  • Docs / website

Tests + verification

  • all fixed paths verified against the tree (test -e: fasten-core/src/redact.rs, catalog.rs, store/{sqlite,postgres}.rs, include/fasten_core.h, bindings/, spec/, tests/)
  • artifact name cross-checked against CI: .github/workflows/fasten-py.yml sets FASTEN_CORE_LIB=.../fasten-core/target/release/libfasten_core.so
  • reference lint: 0 missing path references across CLAUDE.md + the new skill

- the draft file referenced a store-core/ crate that does not exist;
  the Rust core lives at fasten-core/ (lib name fasten_core)
- artifact and header names now match reality: libfasten_core.so and
  include/fasten_core.h, as CI already uses (fasten-py.yml)
- file was previously untracked, so no session on a clean checkout
  ever saw it

Signed-off-by: Himanshu Vimal <himanshu.vimal@gmail.com>
- first project-level skill; points at the CLAUDE.md Commands section
  rather than duplicating it, per the repo-as-router convention

Signed-off-by: Himanshu Vimal <himanshu.vimal@gmail.com>
- src/redact.rs etc were section-relative and ambiguous; now resolvable
  from the repo root, which also makes them lintable

Signed-off-by: Himanshu Vimal <himanshu.vimal@gmail.com>
@cyberwalk3r
cyberwalk3r marked this pull request as ready for review July 19, 2026 01:07
@cyberwalk3r
cyberwalk3r requested a review from praveen-garg July 19, 2026 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants