AI tooling & integrations #79

New Issue

goodboy · 2026-03-05T20:10:54Z

goodboy commented

2026-03-05 20:10:54 +00:00

To start working towards some automation of devving, docs and project management in the land of pikers, originally inspired by my first “productive” session with with claude in #69.

I was inspired me to start now working toward the idealism that we can make working with all AI tools not only seamless but alot of fun for all (potential new) collabs, both newb and core-hacker-degen alike!

Core principles and long run goals

From my PoV specifically, i want to build a persona/character/experience-set for coding aids/“assistants” which,

reflects the interaction of paired programming with a real senior core dev; the entire feel should be like you’re asking for help in one of our chats.
emphasizes a project focused capability set and knowledge base grounded in our core engineering principles:
- conc/queueing/distributed-systems dedicated to hyper-correctness, resiliency and fault tolerance (despite chaotic mkt conditions), poor-performing-code = invalid code, a decentralized-systems-first design.
- a traders-first mentality which dictates the platform should never (or at the least hyper-minimize-for) failures that can lose the user $$ during live trades.
- a scientfic-data-anal/numerics-expert underpinning which drives the design of all supporting and overlying subsystems and ensures low-latency, real-time operation within a distributed and collaborative env; open, performant data sharing/processing/storage/mining is our default use case.
have a very non-corporate “vibe” in all aspects; coding on piker should be fun and chill, something you want to work on for yourself not something you’re getting paid to work on by some overlord..

Provider specific ideas

`claude` Impl deats: groking “skills files”

Originally proposed in #69, the main idea with these (i guess “config”) files is to start maintaining and extending the state of the AI augmented interaction experience.

See the anthropic docs,

https://code.claude.com/docs/en/skills
interaction vibez: https://code.claude.com/docs/en/output-styles
env-based automation: https://code.claude.com/docs/en/hooks-guide
subagents: https://code.claude.com/docs/en/sub-agents
mcp: https://code.claude.com/docs/en/mcp

Of note for me was,

wrt "output styles, being able to have more/less terse/technical feedback depending on your current workflow context:
- while trading we should optimize for noise/distraction-reduction, thinking/reacting fast with zero mental errors.
- while hacking/designing we should emphasize tinkering/researching/profiling and generally having fun with ideas generation and naming.
- while backtesting / testing (auto) strats we should try to be rigorous in our open mindedness and creativity, old ideas aren’t bad but they likely have stopped working (at least at some point) so we should always be mindful of our preset assumptions.
wrt “subagents” building out a set for the bullets listed in the above “core principles” section.
wrt “mcp”, creating services for monitoring/configuring/debugging/coordinating-&-remotely-controlling various actor-daemons in our runtime to enable traders and/or hilevel anal/research users from requiring deep engineering knowledge to manage their (distributed) environment.

I also need to read the docs more thoroughly so likely more to come in follow up as well ;)

TODO others,

opencode which purports to be the best FOSS multi-backend UX?
- https://github.com/anomalyco/opencode?tab=readme-ov-file#faq
- don’t love that it’s ts but..
@goodboy’s very own nascent gish git-service-issue-mgmt xontrib/ which needs to be extended to include wrapping for mgmt of various AI backends to enable,
- easily create/edit/keep-in-contex issues across all supported backend git service APIs
- summarizing issues across all piker-repo (and friend repo) services for any dev that needs a “hi level view” of overall progress / status.

To start working towards some automation of devving, docs and project management in the land of *pikers*, originally inspired by my first "productive" session with with `claude` in #69. I was inspired me to start **now** working toward the idealism that we can make working with all AI tools not only seamless but alot of fun for all (potential new) collabs, both newb and core-hacker-degen alike! --- ## Core principles and long run goals From my PoV specifically, i want to build a persona/character/experience-set for coding aids/"assistants" which, - reflects the interaction of paired programming with a real senior core dev; the entire feel should be like you're asking for help in one of our chats. - emphasizes a project focused *capability set* and *knowledge base* grounded in our core engineering principles: + conc/queueing/distributed-systems dedicated to hyper-correctness, resiliency and fault tolerance (despite chaotic mkt conditions), poor-performing-code = *invalid code*, a *decentralized-systems-first* design. + a traders-first mentality which **dictates** the platform should never (or at the least hyper-minimize-for) failures that can lose the user $$ during live trades. + a scientfic-data-anal/numerics-expert underpinning which drives the design of all supporting and overlying subsystems and ensures low-latency, real-time operation within a distributed and collaborative env; open, performant data sharing/processing/storage/mining is our **default use case**. - have a **very** non-corporate "vibe" in all aspects; coding on `piker` should be *fun and chill*, something *you want to work on for **yourself*** not something *you're getting paid to work on by some overlord*.. --- ## Provider specific ideas ## `claude` Impl deats: groking "skills files" Originally proposed in #69, the main idea with these (i guess "config") files is to start maintaining and extending the state of the AI augmented interaction experience. See the anthropic docs, - https://code.claude.com/docs/en/skills - interaction vibez: https://code.claude.com/docs/en/output-styles - env-based automation: https://code.claude.com/docs/en/hooks-guide - subagents: https://code.claude.com/docs/en/sub-agents - mcp: https://code.claude.com/docs/en/mcp Of note for me was, - wrt "output styles, being able to have more/less terse/technical feedback depending on your current workflow context: + while trading we should optimize for noise/distraction-reduction, thinking/reacting fast with zero mental errors. + while hacking/designing we should emphasize tinkering/researching/profiling and generally having fun with ideas generation and naming. + while backtesting / testing (auto) strats we should try to be rigorous in our open mindedness and creativity, old ideas aren't bad but they likely have stopped working (at least at some point) so we should always be mindful of our preset assumptions. - wrt "subagents" building out a set for the bullets listed in the above "core principles" section. - wrt "mcp", creating services for monitoring/configuring/debugging/coordinating-&-remotely-controlling various actor-daemons in our runtime to enable traders and/or hilevel anal/research users from requiring deep engineering knowledge to manage their (distributed) environment. I also need to read the docs more thoroughly so likely more to come in follow up as well ;) --- ## TODO others, - [ ] `opencode` which purports to be the best FOSS multi-backend UX? * https://github.com/anomalyco/opencode?tab=readme-ov-file#faq * don't love that it's `ts` but.. - [ ] @goodboy's very own nascent `gish` git-service-issue-mgmt `xontrib/` which needs to be extended to include wrapping for mgmt of various AI backends to enable, - easily create/edit/keep-in-contex issues across all supported backend git service APIs - summarizing issues across all `piker`-repo (and friend repo) services for any dev that needs a "hi level view" of overall progress / status.

goodboy referenced this issue

2026-03-05 20:30:20 +00:00

Add `.claude/skills/*` files from gap-annotator perf sesh with ma boi #69

goodboy referenced this issue from a commit

2026-03-05 20:31:04 +00:00

Add `ai/` integration docs w/ `/commit-msg` usage

Sign in to join this conversation.