pikers
/
piker
4
1
Fork 0
Code Issues 20 Pull Requests 11 Packages Projects Releases Wiki Activity
piker/ai
History
Gud Boi ccb6f1913c Add NLNet Commons Fund grant proposal draft 
Draft targeting the NGI Zero Commons Fund (€50k,
deadline April 1 2026) covering all form fields:
abstract, relevant experience, comparison w/
existing efforts, technical challenges, ecosystem
engagement, and budget breakdown.

- frame `piker` as sovereign trading infra for the
  commons addressing a clear market failure in
  proprietary fintech enclosure
- highlight AGPLv3+ copyleft, structured concurrent
  distributed arch via `tractor`/`trio`, zero-web
  philosophy, and venue-agnostic design
- detail 5 deliverable workstreams: runtime
  hardening, broker plugin API, EMS completion,
  packaging/onboarding, and security audit
- include comparison against proprietary platforms,
  permissive-licensed FOSS libs, and institutional
  systems

(this patch was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code
 		2026-03-30 12:16:35 -04:00
..
claude-code Add NLNet Commons Fund grant proposal draft 2026-03-30 12:16:35 -04:00
README.md Add `ai/` integration docs w/ `/commit-msg` usage 2026-03-05 15:30:34 -05: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

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/                  # future
│   └── 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 actual skill source files (under .claude/skills/, etc.) rather than duplicating content