Skip to main content

Use Cases

See how Usable turns team knowledge into shipped work.
Pick a role to follow the step-by-step flow with a preview.

Document and Implement Internal Library

  1. 1

    Author library docs

    You have a private library without documentation. In the repo, ask Usable to create a documentation fragment, focusing on key feature X or Y.

  2. 2

    Consumer asks to implement

    Another developer asks their agent to implement the library in their app.

  3. 3

    Agent finds docs

    The agent searches Usable, finds the documentation fragment, and understands the API and examples.

  4. 4

    First-try implementation

    It implements the library without hallucinations and wires up the key feature.

  5. 5

    Auto-linked knowledge

    After merge, the agent documents the integration. Usable links the docs and implementation via tags and concepts.

.repo/usable – engineer.tsx
repo: internal-lib
$ create documentation fragment focusing on feature X
Usable: created "Internal Lib – Feature X" (type: knowledge)
$ implement internal-lib feature X
→ Agent: found fragment, generating edits…
→ PR ready. Linked with tags: library, feature-x

Provision Databases with Secure Crossplane CRDs

  1. 1

    Develop secure CRDs

    DevOps engineers build Crossplane CRDs encoding company best practices for secure Postgres/MySQL across supported clouds.

  2. 2

    Document CRDs & spec

    Ask the LLM to create fragments that document the CRD itself (schema/fields, validation, examples) and also extract best practices and security constraints.

  3. 3

    Provision database

    A developer asks the agent to set up a Postgres database on AWS.

  4. 4

    Apply best-practice profile

    The agent finds the relevant fragments (e.g., Azure/AWS profiles), generates YAML, and runs kubectl to apply the CRD configuration.

  5. 5

    Capture issues for reuse

    Any issues discovered during provisioning are captured as solution fragments for future sessions.

provision.yaml
# Fragment: PostgresInstance CRD (excerpt)
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: postgresinstances.database.example
spec:
  group: database.example
  names:
    kind: PostgresInstance
  versions:
  - name: v1
    schema:
      openAPIV3Schema:
        properties:
          spec:
            properties:
              profile: enum[aws-secure, azure-secure, gcp-secure]
              storageGiB: integer
              highAvailability: boolean
# Example resource
apiVersion: database.example/v1
kind: PostgresInstance
metadata:
  name: app-prod
spec:
  profile: aws-secure
# $ kubectl apply -f crossplane/app-db.yaml
# → Applied secure profile; docs + spec linked in fragment

Onboard Teams and Scale Standards

  1. 1

    Teach the LLM

    Team members teach the LLM best practices, tech stack, and patterns; the LLM creates learnings as fragments.

  2. 2

    Onboard fast

    New members scaffold and ship code guided by the agent, with comparisons to team standards.

  3. 3

    10× delivery

    Existing members move faster with the team's combined knowledge of services, libraries, and deployments.

onboarding.md
# Team Onboarding Checklist
- Install dependencies
- Connect IDE to Usable
- Read 'Frontend Standards' fragment
- Ask agent: scaffold dashboard page

Ready to give your team shared memory?

Start building with AI agents that remember everything. Free tier available — no credit card required, no complex setup.