pikers
/
piker
4
1
Fork 0
Code Issues 20 Pull Requests 13 Packages Projects Releases Wiki Activity
piker/ai
History
Gud Boi a26e060c3a Skip stale trade ticks in 1s sampler 
Queued IB startup trades can arrive after samplerd has advanced
the current 1s bar. Writing them into that bar creates a false
price and volume spike. Compare each stamped trade with the
current bar before updating either SHM buffer. Warn whenever a
next-slot trade must wait for samplerd; skip other mismatches
and leave untimestamped feeds on the receive-time path.

Add focused tests for epoch units, queued trades, and warning
before the next-slot wait. Note that incomplete provider bars
still need a correction path for late trades.

Prompt-IO: ai/prompt-io/codex/20260925T190523Z_c0dae89a_prompt_io.md

(this patch was generated in some part by `codex` using `gpt-6` (`openai`))
 		2026-09-25 17:54:42 -04:00
..
claude-code Add `piker-clearing-expert` skill 2026-08-27 23:24:54 -04:00
opencode Add `piker-clearing-expert` skill 2026-08-27 23:24:54 -04:00
prompt-io Skip stale trade ticks in 1s sampler 2026-09-25 17:54:42 -04:00
README.md Add `piker-clearing-expert` skill 2026-08-27 23:24:54 -04:00

README.md

AI Tooling Integrations

Documentation and usage guides for AI-assisted development tools integrated with this repo.

Each subdirectory corresponds to a specific AI tool or frontend and contains usage docs for the custom skills/prompts/workflows configured for it.

Originally introduced in PR #69; track new integration ideas and proposals in issue #79.

Integrations

Tool Directory Status
Claude Code claude-code/ active
OpenCode opencode/ active

Shared Skills

Provider-neutral skill bundles should use the portable Agent Skills subset and live under .agents/skills/ as their single source. OpenCode discovers that project directory natively. Relative links in provider directories such as .claude/skills/ may bridge clients which do not yet scan .agents/skills/; never copy the skill body.

Existing repo skills under .claude/skills/ predate this convention and can migrate separately without coupling their history to new skills.

Harness-specific command files should only delegate to a shared skill. They must not duplicate the skill body.

Adding a New Integration

Create a subdirectory named after the tool (use lowercase + hyphens), then add:

  1. A README.md covering setup, available skills/commands, and usage examples
  2. Any tool-specific config or prompt files
ai/
├── README.md                  # <- you are here
├── claude-code/
│   └── README.md
├── opencode/
│   └── README.md
└── <your-tool>/
    └── README.md

Conventions

  • Skill/command names use hyphen-case (commit-msg, not commit_msg)
  • Each integration doc should describe what the skill does, how to invoke it, and any output artifacts it produces
  • Keep docs concise; link to the shared skill source files rather than duplicating content
  • Keep skill bodies harness-neutral; isolate slash-command syntax and permissions in each harness integration