FT AI Toolkit

One home for how Friendly Technologies builds software with AI: the engineering standards each team follows and every agent enforces, the agents & skills themselves, and how to deploy and use them.

Repository — Friendly-Technologies/ft-ai-toolkit (default branch main) is the canonical source of truth. Nothing auto-installs; sync into ~/.claude on demand.

git clone https://github.com/Friendly-Technologies/ft-ai-toolkit.git
cd ft-ai-toolkit
DRY_RUN=1 deploy/scripts/install.sh   # preview → run without DRY_RUN to install skills & agents

New here? Read RESUME.prompt.md first; full setup in Deployment & Usage.

Pick your standard

The backend and frontend are built by different teams, so the standard is split — read only yours. They meet at the API contracts: the internal UI↔BE wire and the external REST API.

Guide What’s inside

1. Java / Spring Boot

For backend engineers. Packages-as-catalog, naming, DI, records, structured greppable logging (deviceId/sessionId — no MDC), tests & TDD, the MySQL/Oracle DB contract, protocol-as-truth.

2. Angular Frontend

For frontend engineers. Folders-as-catalog with barrels, naming, immutability/NgRx, NgModule/OnPush, logging via the app logger, the kept permissive style.

3. Internal API (UI↔BE)

The internal POST-RPC wire — envelopes, error codes, URL style, identity, per-operation verbs. Hand-kept, no codegen.

4. External API (REST)

The outward-facing REST + OpenAPI contract for northbound / public / integration consumers (*RestRequest/*RestResponse, StatusResponse, JWT, real HTTP status).

Ways of working

Guide What’s inside

SDD · TDD · Agentic

When to spec-first, when to test-first, and how the agentic engine runs both — on diagrams, with a decision flow and live examples.

Writing an SDD

The one-page spec: section-by-section rules + a full worked example.

The toolkit

Guide What’s inside

Claude Toolkit

The agents and skills: what each does, when it fires, and who-runs-whom. Orchestration diagrams.

Knowledge Base

The Qdrant vector store the agents query for grounding — what each collection holds, who uses it, when.

Knowledge Vault

The shared Obsidian vault the agents read at the start of a task and write to at the end — the team’s cross-session memory of root causes and decisions.

Deployment & Usage

Local setup, the component-map CI gates, and copy-paste prompts that exercise the agents.

Reference

  • Glossary — FT, protocol, and standard terms used across these pages.

The one idea

A single platform standard, split per team, enforced automatically, meeting at one contract.

Standard Team Highlights

Java / Spring

backend

packages, records, DI, greppable logs, DB contract, protocol-as-truth

Angular

frontend

folders/barrels, NgModule/OnPush/NgRx, logging, style

Internal API

UI↔BE

POST-RPC envelopes, error codes, identity

External API

northbound

REST + OpenAPI, StatusResponse, JWT
Start with your team’s standard, then skim the contract you share with the other.