Skip to content

Instantly share code, notes, and snippets.

View kingargyle's full-sized avatar

David Carver kingargyle

63 followers · 18 following
View GitHub Profile
@kingargyle
kingargyle / skills_protocol.md
Created March 15, 2026 22:00
Agent SKILLS Protocol that helps implement the agentskills.io specification to Agents that Don't support it

[SPEC] Agent Skills Integration (agentskills.io Standard)

Goal

Implement the agentskills.io standard into the project's Phased Spec-Driven Development (SDD) protocol. This enables modular, pull-on-demand expertise discovery and activation, ensuring context economy while providing specialized agent capabilities.

Context

  • Current State: The project uses a Phased GSD protocol defined in prompts/plans/sdd_implementation_v1.md. All agent instructions are currently static and centralized.
  • Constraints: Must work with non-native skill loaders (Android Studio Gemini/Otter). Must preserve the "Memory Protocol" and subdirectory structure for plans.
  • Files:
  • prompts/plans/sdd_implementation_v1.md (Target for update)
@kingargyle
kingargyle / skills_capability_prompt.md
Last active March 14, 2026 20:38
Skill Capability for SDD

Using the protocol in prompts/sdd_implementation_v1.md as a base, perform a "Phase 0: Agent Skills Integration" update to that file.

Update the document to Version 2.2.0 with the following mandatory architectural changes to support the agentskills.io standard:

  1. FORMAL AGENT SKILLS DISCOVERY (v2.2.0):
    • Protocol Update: Define a specific "Skill Discovery" phase for agents that do NOT natively support external skill loaders (e.g., Android Studio Otter, Gemini, Copilot).
    • Storage Standard: All skills must reside in prompts/skills/<skill-name>/.
    • File Structure: Each folder MUST contain a single SKILL.md file (the interface) and optional scripts/ or references/ directories.
    • The Discovery Step: At the start of every session, the agent MUST execute list_files on prompts/skills/ to identify available expertise.
@kingargyle
kingargyle / agent_tool_discover.md
Last active March 14, 2026 19:43
Agent Tools Discovery

[SPEC] Agent Tool and Capability Discovery

Goal

  • To systematically discover and document all features, tools, MCP servers, sub-agent support, skills (agentskills.io), and commands that the current agent environment reports to the LLM.
  • Generate structured reports for each discovered category in the discovered_artifacts directory.

Context

  • Current State: The agent has access to a variety of tools (standard and MCP-based), but there is no centralized documentation of these capabilities within the project for reference.
  • Constraints: Must follow SDD v2.0 protocol. Reports must be generated without violating "Reporting Constraints" (except as requested for this specific discovery task).
  • Files:
  • prompts/plans/agent_tool_discovery/agent_tool_discover.md (This spec)
@kingargyle
kingargyle / sdd_test_prompt.md
Created March 12, 2026 01:38
Test Suite for SDD

Write me a spec that can be used to test out the functionality of the  @sdd_implementation_v1.md  or any general SDD implementation. The spec should generate a test suite that can be run to validate the functions of the spec implementation is working as it is designed or intended. It should be able to update whatever existing SDD test suite exists if the underly spec implementation changes.

License

MIT License Copyright (c) 2026 David Carver and NineWorlds

@kingargyle
kingargyle / context_discovery.md
Created March 4, 2026 02:39
Project Context Discovery

[SPEC] Standardized Context Discovery

Goal

Formalize "Tribal Knowledge" into "Golden Standards" through a heuristic-based discovery process. This plan identifies architectural "Gravity Wells," documents anti-patterns, and maps cross-module protocols to ensure consistency and formalize project intelligence in a language/framework-agnostic manner.

Context

  • Current State: The project has implementation-defined standards that may be implicitly understood but lack formal documentation in AI system prompts.
  • Constraints: This plan is language and framework agnostic. The executing agent must determine the specific tech stack through probing and adapt its discovery methodology accordingly.
  • SDD Memory: All findings, surprising dependencies, and architectural debt must be logged in prompts/plans/context_discovery/memory/.
@kingargyle
kingargyle / TOOLING_CONSTRAINTS.md
Created February 24, 2026 02:49
AI Tooling Constraings

AGENT CAPABILITY PROTOCOL

1. Filesystem Fallbacks

  • No Directory Creation Tool: Use your Write tool to create a placeholder .gitkeep file in the target path.
  • No Delete/Move Tools:
    1. Write the new file to the destination.
    2. Add the old file path to the "Cleanup & Manual Actions" section of the task spec for human action.

2. Environment Restrictions

  • No Direct Shell: Do not assume shell access (bash/zsh).
@kingargyle
kingargyle / sdd_implementation_v1.md
Last active March 7, 2026 04:47
Enforce Spec Driven / Goal Driven development

Implementation Plan: Phased Spec-Driven Development (SDD)

Status: PROPOSED
Version: 2.1.0
Target: Standardized AI Workflow (Universal LLM/Agent Compatibility)

1. Scope and Summary

  • Scope: This protocol applies to all AI-assisted development (features, refactors, migrations).
  • Summary: To eliminate "Vibe Coding" and ensure consistency, this plan implements a Spec-First Protocol. Agents must generate a Phased GSD (Goal, Steps, Deliverables) document before writing any production code for complex tasks.
  • Context & Memory: v2.0 introduces persistent context management. Each plan resides in its own directory, with a dedicated memory/ sub-folder to record findings, unexpected dependencies, and state changes across execution phases.
@kingargyle
kingargyle / promptslocation.md
Created February 16, 2026 14:59
Location of Android Studio Prompts

On a a linux system, the app.prompts.xml file that contains the saved prompts, is stored in `~/.config/Goggle/AndroidStudioVersion/options/app.prompt.xml'

For MacOSX: Configuration/Settings: ~/Library/Application Support/Google/AndroidStudio

  • Plugins: ~/Library/Application Support/Google/AndroidStudio/plugins
  • System/Cache Files: ~/Library/Caches/Google/AndroidStudio
  • Logs: ~/Library/Logs/Google/AndroidStudio

For Windows: On Windows, the settings are stored within the user's AppData folder:

@kingargyle
kingargyle / pipewire.md
Created May 2, 2025 23:54 — forked from the-spyke/pipewire.md
Enable PipeWire on Ubuntu 22.04

Enable PipeWire on Ubuntu 22.04

This guide is only for original Ubuntu out-of-the-box packages. If you have added a custom PPA like pipewire-debian, you might get into conflicts.

Ubuntu 22.04 has PipeWire partially installed and enabled as it's used by browsers (WebRTC) for recoding the screeen under Wayland. We can enable remaining parts and use PipeWire for audio and Bluetooth instead of PulseAudio.

Starting from WirePlumber version 0.4.8 automatic Bluetooth profile switching (e.g. switching from A2DP to HSP/HFP when an application needs microphone access) is supported. Jammy (22.04) repos provide exactly version 0.4.8. So, we're good.

Based on Debian Wiki, but simplified for Ubuntu 22.04.

@kingargyle
kingargyle / End GCode
Last active February 9, 2024 10:35
Prusa Slicer Anycubic Kobra Neo
M117 Cooling down...
M104 S0 ; turn off extruder
M107 ; Fan off
M140 S0; Turn bed off
M84 ; disable motors
G91 ;relative positioning
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 ;X-20 Y-20 F240 ;move Z up a bit and retract filament even more
G28 X0 ;move X to min endstops, so the head is out of the way
G90 ;Absolute positionning