Skip to content

zendev-lab/ulota / .agents/skills/spark-agent-knowledge

spark-agent-knowledge

Verified

Use when Spark engineering knowledge must be placed, deduplicated, migrated, or validated across AGENTS, Notes, Roles, Skills, and Workflows.

Spark agent knowledge

Apply one home per fact and progressive disclosure.

Classification

Use agent knowledge instructions for asset ownership and loading rules, and CONTRIBUTING.md for public documentation ownership.

Procedure

  1. Locate the enforced or runtime owner of each fact and existing copies.
  2. Classify each fact before editing; link to the authoritative home instead of restating details.
  3. Keep Role bodies free of methods owned by Skills. Keep Workflows free of specialist implementation instructions.
  4. Update all active inbound links atomically and leave archived public docs unchanged unless explicitly requested.
  5. Run the repository agent-knowledge and documentation checks that apply.

Preserve the runtime-context and public-documentation boundaries. Reconcile stale prose with verified enforced contracts; escalate a conflict only when resolving it requires a product or authority decision. Return classification, authoritativeHomes, moves, linksUpdated, validation, and blockers.

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: 466kUpdated Claude CodeCodexVerifiedInstall
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: 466kUpdated Claude CodeCodexVerifiedInstall
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: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall