DataArt/artisyn-implementation-harness / skills/implementation-harness
implementation-harness
FlaggedInstall the portable AI-dev harness, rebuild its operational graph standalone, harvest project skill improvements into its canonical templates, package direct canonical edits into a portable bundle, or apply canonical updates to an existing project. Use /implementation-harness launch, /implementation-harness reindex-graph, or /implementation-harness patch harvest|prepare|apply.
bin/lib/providers.mjs
View on GitHub/** The three hosts the package installs into, and how each one names things. */
import fs from 'node:fs';
import path from 'node:path';
export const PROVIDERS = {
claude: { dir: '.claude', skills: '.claude/skills', prefix: '/' },
codex: { dir: '.agents', skills: '.agents/skills', prefix: '$' },
copilot: { dir: '.github', skills: '.github/skills', prefix: '/' },
};
export const PROVIDER_NAMES = Object.keys(PROVIDERS);
export const PACKAGE_FOLDER = 'implementation-harness';
/** Providers to install for. Flags win and keep their order; otherwise every host folder that
* already exists in the project, in the order claude, codex, copilot.
*/
export function detectProviders(root, requested = []) {
if (requested.length > 0) {
for (const name of requested) {
if (!PROVIDERS[name])
throw new Error(`Unknown provider "${name}" (expected ${PROVIDER_NAMES.join(', ')})`);
}
return [...new Set(requested)];
}
return PROVIDER_NAMES.filter((name) => fs.existsSync(path.join(root, PROVIDERS[name].dir)));
}
export const skillsFolder = (provider) => PROVIDERS[provider].skills;
/** A command in the provider's own syntax, e.g. `/implementation-harness launch` or
* `$implementation-harness patch apply` for Codex.
*/
export const command = (provider, route) =>
`${PROVIDERS[provider].prefix}${PACKAGE_FOLDER} ${route}`;
export const launchCommand = (provider) => command(provider, 'launch');
/** The provider whose skills folder holds `packageDir`, or `claude` when none does. */
export function providerOfPath(root, packageDir) {
const found = PROVIDER_NAMES.find((name) => {
const rel = path.relative(path.join(root, skillsFolder(name)), packageDir);
return rel !== '' && !rel.startsWith('..') && !path.isAbsolute(rel);
});
return found ?? 'claude';
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |