Commit Graph
15 Commits
Author SHA1 Message Date
Willie fd3bc824f3 feat(targets): edit other files a target's tool reads from its page
Pi and OMP read APPEND_SYSTEM.md next to their skills, and editing it
meant leaving the dashboard. A target page now shows extra file tabs:
built-in ones come from targets.yaml `files:` (APPEND_SYSTEM.md for pi
and omp), and users can add their own, including files in subfolders.
Paths stay inside the tool's folder; three tabs show and the rest move
to a menu. "Share with Extras" opens Add extra prefilled with the file's
folder and name, so the same file can be shared across tools.

A single-file extra's name now defaults to its file name without the
extension (APPEND_SYSTEM.md -> APPEND_SYSTEM) until the user types one,
and the hint suggests the file name, as the #300 reporter asked.

Refs #301
Refs #300
2026-09-29 15:25:06 +08:00
Willie b8291895e1 feat(ui): share one AGENTS.md across tools from the dashboard
Claude Code now reads AGENTS.md, but every tool still keeps its standing
instructions in its own file (CLAUDE.md, GEMINI.md, AGENTS.md), and Claude
has no user-level AGENTS.md at all. Keeping several tools on the same
instructions meant copying text between those files by hand.

Each target page gets a tab named after the file it reads, with its read
order, an editor, and a convert flow from CLAUDE.md to AGENTS.md. In global
mode the Extras page gets an AGENTS.md tab where several shared files can
coexist and each target picks one or keeps its own. Shared files are
single-file extras: tools that follow @imports get a managed import block
and keep their own lines, others get a link in place of their file.
Projects get small shims instead, since every tool there reads ./AGENTS.md.
Custom targets can declare which file they read.

Restore records the target's state when it is first attached (file,
symlink, or no file) and always returns to it. Edits made after attaching
are kept as drift backups instead of becoming the restore point, so sync,
reapply and mode switches can no longer lose the user's original file.
2026-09-27 03:02:51 +08:00
Willie bb57a9af9c feat(targets): add account targets for a second Claude, Codex or Pi config directory
A target declared with `agent` and `config_dir` is another config directory of a
built-in Agent, such as a second Claude account. Its skills and agents paths are
derived from the Agent's defaults at load time, so the config only records the
directory. The same target name works for MCP (written in the Agent's format into
the account's own file), for plugins (the Agent CLI runs with CLAUDE_CONFIG_DIR,
CODEX_HOME or PI_CODING_AGENT_DIR) and for `mcp import --from`. Removing such a
target warns when MCP config still names it instead of failing later at sync.

The dashboard gains an "another account" mode in the add-target dialog and lists
accounts next to the Agents on the MCP and plugin pages.

Refs #289
2026-09-22 11:21:35 +08:00
Willie 502873ed41 refactor(targets): detect tools and overlaps independently of the default skills path
Several tools now document the shared ~/.agents/skills directory as their
primary skills path. Moving a built-in target there would break three things
that assume a tool-specific path: init and the dashboard detect an installed
tool through the parent of its skills path, and the overlap checks only
consult also_scans, so configs pinned to the old path would silently lose
their duplicate-skill warning.

Add an optional `detect` install dir per target and derive overlap checks
from every path a runtime reads (also_scans plus the built-in default),
skipping the target's own configured path. No default changes here, so
behaviour is unchanged until a target opts in.

Refs #135
2026-09-21 02:06:47 +08:00
Willie f9be84c0f5 feat(projects): manage project folders from the global config
People with many repositories had to choose between listing every
project skills folder as a custom target or running project mode in
each repo. A `projects:` key in the global config now declares a folder
once with the tools used there, and sync treats each one as a
`<project>@<tool>` target with its own mode and filters.

- Expand `projects:` into virtual targets at load time and strip them
  on save; tools that share a project skills folder are written once
- Skip a project whose folder is missing with a warning instead of
  failing the whole sync; `collect` and `target` ignore project targets
- Add /api/projects (list, save, remove, convert) and detect ordinary
  targets that already point inside a project so they can be converted
- Add a Projects page to the dashboard with Skills, Agents and MCP tabs
  per project, replacing the Projects tab on the MCP page
- Extend Select with a multi-select mode for picking a project's targets

Refs #286
2026-09-21 01:52:34 +08:00
Willie 59754ca3e6 fix(sync): resolve agent target aliases 2026-06-11 01:32:34 +08:00
Willie 88a1bd50a4 feat(doctor): warn on shared paths and cross-target discovery
Add two new doctor checks to detect duplicate-skill problems
surfaced in issue #135:

Layer 1 — checkSharedTargetPaths:
  Warns when two or more enabled targets resolve to the same
  filesystem path after tilde expansion. Pure metadata check; no
  runtime probing. Catches universal/warp/witsy all sharing
  ~/.agents/skills.

Layer A — checkCrossTargetDiscovery:
  Driven by a new also_scans field in targets.yaml that documents
  paths a target's runtime reads beyond its primary skills
  directory. Sourced from each tool's official docs. Populated
  for amp, antigravity, codex, cursor, firebender, kimi, roo.

  Warns when an enabled target's also_scans path is the primary
  path of another enabled target. Example: enabling codex +
  universal warns that Codex's runtime will see ~/.agents/skills
  content.

  Overlaps are grouped per scanner so a multi-overlap target
  (e.g. firebender reading 5 brand dirs for cross-compat) emits
  a single warning with indented detail lines.

config:
  - New targetAlsoScans struct + AlsoScansGlobal / AlsoScansProject
    accessors.
  - targets.yaml schema is backward-compatible (optional field).

Layer B (sync engine routing) and Layer C (user-declared
authoritative roots) are intentionally deferred — diagnosis comes
first, behaviour changes only if users actually ask.
2026-05-21 23:49:40 +08:00
Willie f0f15ce15a refactor(targets): restructure targets.yaml to nested per-kind format
Unify global_name/project_name into single name field and move flat
paths into skills: { global, project } nested block. All 56 targets
converted with zero public API signature changes.

Add targetPathPair sub-struct and agents: block for v1 agent targets
(claude, cursor, opencode, augment). New DefaultAgentTargets() and
ProjectAgentTargets() functions return only targets with agent paths.

Update all internal consumers: DefaultTargets, ProjectTargets,
LookupProjectTarget, GroupedProjectTargets, MatchesTargetName,
KnownTargetNames, resolveTargetPaths, ProjectTargetDotDirs.

ProjectTargetDotDirs now collects dot-dirs from both skill and agent
project paths to prevent discovery from scanning agent target copies.
2026-03-30 18:32:33 +08:00
Willie 5369595bc1 fix(install): skip target dotdirs during skill discovery
Repos like pbakaus/impeccable commit .claude/skills/ alongside their
source skills, causing discoverSkills to find every skill twice (36
instead of 18). Fix by deriving known target dotdir names (.claude,
.cursor, .skillshare, etc.) from targets.yaml project_path values and
skipping them during filepath.Walk.

Non-target hidden dirs (.curated, .system — used by openai/skills) are
still discovered as before. Injection pattern avoids circular import
between config and install packages.
2026-03-12 16:45:02 +08:00
Willie a05d3448f2 fix(sync): match targets by shared path and track local dirs in prune
MatchesTargetName now falls back to path comparison when name-based
matching fails, so targets sharing the same project_path (e.g. codex
and universal both using .agents/skills) correctly match in
FilterSkillsByTarget.

PruneOrphanLinks records user-created directories in LocalDirs instead
of emitting misleading "unknown directory" warnings, and syncMergeMode
counts them toward the local skill total.
2026-02-25 07:02:54 +08:00
Willie be9ac8945c refactor(targets): rename agents→universal, fix kimi/replit paths
- Rename "agents" target to "universal" with backward-compat alias
- Fix kimi global_path: ~/.kimi/skills → ~/.config/agents/skills
  (matches official docs recommended path)
- Add replit global_name and global_path (~/.config/agents/skills)
- Prefer "universal" as canonical name in GroupedProjectTargets
- Update tests for new naming and kimi as universal group member
2026-02-20 13:59:34 +08:00
Willie 403aafb254 feat: unify project target names with global names, add aliases for backward compat
Project targets now use the same short names as global targets (e.g.,
"claude" instead of "claude-code"). Old project_name values are preserved
as aliases so existing configs continue to work.

- Add Aliases field to targetSpec (deprecated, remove once safe)
- Update 11 targets in targets.yaml: project_name = global_name
- LookupProjectTarget falls back to alias lookup
- Fix 3 callers that bypassed LookupProjectTarget
- Extend MatchesTargetName and KnownTargetNames with alias support
- Add TestLookupProjectTarget_Alias
- Update all integration tests, docs, CLI help, and FAQ
2026-02-16 00:08:59 +08:00
Willie a29e198725 feat: add target filter CLI, skill-level targets field, and Web UI support
- CLI: `target <name> --add-include/--add-exclude/--remove-include/--remove-exclude`
- SKILL.md `targets` frontmatter restricts sync to specified targets
- Cross-mode matching (e.g. "claude" matches "claude-code" project target)
- Web UI: inline filter editor on Targets page, target badges on Skills pages
- API: PATCH /api/targets/{name} for filter updates
- Fix drift detection in doctor/status/handler to account for skill-level targets
- `check` warns about unknown target names in skill-level targets field
- Docs: update skill-format, target command, configuration, creating-skills
2026-02-15 23:29:30 +08:00
Willie 57e7b68131 feat: group shared-path agents in project init UI
Multiple agents (Amp, Codex, Copilot, Gemini, Goose, Kimi, OpenCode,
Replit) all map to .agents/skills in project mode. Previously init -p
showed each as a separate selectable entry pointing to the same directory,
which was redundant and confusing.

Now targets sharing a project path are collapsed into a single group entry
(e.g. "agents") with member names shown in parentheses. Discover uses
path-based dedup so an existing "amp" entry correctly prevents the
"agents" group from appearing as new. --select accepts both canonical
and member names for backward compatibility.

- Add project_name/project_path to agents meta-target in targets.yaml
- Add GroupedProjectTargets() in config package with unit tests
- Rewrite detect/list/prompt/discover in init_project.go
- Add agents target to playground demo project
2026-02-13 14:21:36 +08:00
Willie b83300ac05 feat: project level skills 2026-02-05 11:20:53 +08:00