Skelly Skelly

Skelly

Know your software to its bones.

Scroll

Your product lives in a lot of different heads at once. Every role has their own tools. Their own view. The full picture lives across all of them — and nowhere at once.

Skelly reads your code and builds a complete picture of your product — structured, always current — that every person and every tool on your team draws from.

Product Explore ideas and propose features in plain language. See how they connect to everything else.
Design Understand constraints. See decisions in the context of the whole system.
Engineering Know the intent before writing a line. Full architecture, always current.
QA Report bugs in context. Know exactly what changed, why, and what to validate.
AI Full product context across every discipline, always. Every team member's AI has the whole picture — no more starting from scratch.

Your whole product. Known to the bones.

What Skelly builds

Skelly reads your code and generates a structured, plain-language picture of your entire product. Anyone on the team can open it. It stays current automatically.

app.skelly.ai / model
Authentication
Last updated 2 days ago via "Add Stripe billing"
GitHub OAuth2 sign-in. Sessions use JWT cookies (30-day TTL) carrying user role and subscription tier.
Billing
Added 2 days ago
Monthly plans via Stripe Checkout. Customers manage subscriptions at /settings/billing. Tracks plan, status, and invoices.
Settings
Last updated 5 days ago via "Sidebar nav for settings"
Sidebar layout with sections: Profile, Team, Notifications, Billing. Collapses to dropdown on mobile.

Not documentation. Not a wiki.
The single source of truth your team has never had.

How it works

See the full product without code
Skelly maps your entire product in plain language — architecture, features, data model. Always current, never stale. No engineering background required.
Brainstorm with full context
Explore ideas with an AI that knows your entire product. Every suggestion is grounded in what you've already built — not generic. Promising ideas become proposals with one click.
From idea to shipped
Go from brainstorm to scoped proposal to merged code. Every change is traced end to end — you always know what was proposed, what shipped, and how the product evolved.
app.skelly.ai / backbone
BACKBONE · acme-app
Product overview
◆ Architecture
◇ Monorepo · Turborepo + pnpm workspaces
◇ API · REST + server-sent events
◆ Authentication
◇ GitHub OAuth2 · JWT sessions
◆ Features
◇ Dashboard · Backbone viewer
◇ Change proposals · Diff-based review
◇ Billing · Stripe subscriptions
app.skelly.ai / ideas
What would it take to add a referral program?
sk
Based on your current model, here's what I'd consider:

You already have:
· Stripe billing with subscription management
· User auth with role-based tokens

You'd need:
+ Referral codes tied to user accounts
+ Stripe coupon API for credits/discounts
+ Referral status in the settings sidebar

This builds on Billing and Authentication — no new infrastructure.
app.skelly.ai / changes / referral-program
Delivered Add referral program
Idea Mar 18 · Proposed Mar 19 · Delivered Mar 21 · model updated
sk
skelly-bot
Model updated · New section: Referrals
Billing updated · coupon integration added
Data Model updated · Subscription + Invoice tables
See the system your designs live in
Understand constraints, patterns, and architecture — without digging through code. Skelly shows you the real system, not what someone remembers from last sprint.
Design decisions that land
Propose changes through conversation with an agent that knows what's technically possible and what your change affects across the whole product.
Stay aligned with what shipped
Skelly always reflects the real product. No drift between what was designed and what was built — you're always working from the truth.
app.skelly.ai / backbone / features
BACKBONE · acme-app · Features
Settings
The settings page uses horizontal tabs with 3 sections: Profile, Team, and Notifications.
Layout follows the app shell pattern — fixed sidebar, scrollable content area. All forms use inline validation.
Dashboard Settings Billing Proposals
app.skelly.ai / propose
The settings page needs a sidebar nav instead of tabs — it's getting too crowded as we add more sections.
sk
Looking at the backbone, settings currently uses horizontal tabs with 3 sections. A sidebar would affect layout and navigation patterns.

Backbone changes:
+ Settings layout: tabs → vertical sidebar
+ Sidebar collapses to dropdown on mobile
~ Navigation pattern updated across Settings
app.skelly.ai / backbone / features / settings
BACKBONE · acme-app · Features
Settings
Last updated 1 day ago via "Sidebar nav for settings"
The settings page uses a vertical sidebar with sections: Profile, Team, Notifications, and Billing.
On viewports below 768px, the sidebar collapses to a dropdown selector.
Living docs that stay current
Architecture, conventions, data model — always accurate, always up to date. It evolves with your product so documentation is never a separate chore.
Full intent behind every change
See what was proposed and why, not just the diff. Every change carries context that survives the pull request — so you never lose the "why."
AI that knows your stack
Implementation that follows your conventions, patterns, and architecture. Not generic autocomplete — informed, contextual code that fits your codebase.
app.skelly.ai / backbone / view
BACKBONE · acme-app · v0.5.0
Authentication
Last updated 2 days ago via "Add Stripe billing"
Users authenticate via GitHub OAuth2. Sessions are managed with JWTs stored in httpOnly cookies with a 30-day TTL.
The JWT payload includes userId, role, email, and subscriptionTier.
Authentication Billing Data Model Features
app.skelly.ai / changes / billing
CHANGE · Add Stripe billing
Proposal context
Requested by: product · Mar 12
Intent: Monthly subscription plans with a self-serve portal. Customers should be able to upgrade, downgrade, and view invoices without contacting support.
Scope: New Billing section in backbone. Touches Authentication (subscription tier in JWT) and Data Model (Subscription + Invoice tables).
Pull requests
Open skellyLabs/api #48 feat: Stripe billing + customer portal
app.skelly.ai / propose
Add Stripe billing.
sk
Your architecture uses Hono on Node with JWT sessions and Prisma on PostgreSQL. Here's a proposal that fits your patterns:

Backbone changes:
+ Stripe Checkout (matches existing OAuth redirect pattern)
+ New Prisma models: Subscription, Invoice
+ Customer portal at /settings/billing
+ Subscription tier added to JWT payload

Following your conventions — REST endpoints, Prisma migrations, React with inline styles.
Know exactly what changed
Skelly tracks every change with full context — what was proposed, what was implemented, and what it touched. No more hunting through tickets and PRs.
Bugs that fix themselves
Report an issue and Skelly finds the gap — what should happen versus what actually does. Bugs get categorized, linked to the right sections, and can become fix proposals automatically.
Full product map for testing
Understand how features connect, what a change could affect, and what needs regression testing — all without reading source code.
app.skelly.ai / changes
RECENT CHANGES
Add Stripe billing · Billing, Authentication, Data Model
Sidebar nav for settings · Features › Settings
Fix empty state on billing · Features › Billing
3 changes this week · 5 backbone sections affected
app.skelly.ai / bugs
BUGS · acme-app
HIGH Blank screen on /settings/billing Model gap: no empty state for Billing when subscription is null Billing · Authentication · 2 sections affected
MED Sidebar nav doesn't collapse on mobile Expected: dropdown below 768px · Observed: sidebar overflows Features › Settings · 1 section affected
app.skelly.ai / backbone
BACKBONE · acme-app · Dependencies
Billing
Connected sections
◆ Billing
→ Authentication · subscription tier in JWT
→ Data Model · Subscription + Invoice tables
→ Features › Settings · billing tab in sidebar
→ Features › Dashboard · plan badge display
Full context, every session
Architecture, conventions, intent — AI never starts from scratch. Skelly gives it a structured understanding of your entire product from the first prompt.
Your patterns, not generic code
AI writes code the way your team does — same stack, same conventions, same structure. Implementation that fits, not boilerplate that needs rewriting.
Gets smarter as you build
Every accepted change makes Skelly richer. The more your team builds, the more context AI has — and the better it gets at helping everyone.
app.skelly.ai / backbone
AI CONTEXT · acme-app · Full backbone loaded
What AI knows
◆ Architecture · monorepo, Hono API, React frontend
◆ Authentication · GitHub OAuth2, JWT sessions
◆ Data Model · PostgreSQL, Prisma ORM, 12 models
◆ Conventions · REST endpoints, inline styles, Prisma migrations
◆ Features · 6 sections, 14 sub-features
◆ Change history · 23 delivered proposals
app.skelly.ai / propose
Add Stripe billing.
sk
Your architecture uses Hono on Node with JWT sessions and Prisma on PostgreSQL. Here's a proposal that fits your existing patterns:

Backbone changes:
+ Stripe Checkout (matches existing OAuth redirect pattern)
+ New Prisma models: Subscription, Invoice
+ Customer portal at /settings/billing
+ Subscription tier added to JWT payload

Following your conventions — REST endpoints, Prisma migrations, React with inline styles.
app.skelly.ai / backbone / history
BACKBONE GROWTH · acme-app
Evolution
v0.1.0 · Initial backbone · 3 sections
v0.3.0 · +Dashboard, +Proposals · 5 sections
v0.5.0 · +Billing, +Settings sidebar · 6 sections
23 changes delivered · AI context grows with every one

Connect any AI agent

Your entire product, available to every tool on your team. One URL. Full context.

MCP Client Config JSON
{ "mcpServers": { "skelly": { "url": "https://mcp.skelly.ai?token=sk_live_..." } } }
One URL, full context
Point any MCP-compatible client at your Skelly server. Claude, Cursor, Windsurf, your own tools — they all get the same complete picture.
Ask, don't dump
Agents query your backbone through natural language. No need to paste entire specs into context windows — Skelly answers with exactly what's relevant.
Scoped API tokens
Generate tokens from your account settings. Revoke anytime. Every tool gets its own key with usage tracking built in.

Works with any client that supports the Model Context Protocol

The skeleton walks soon

Star the repo. The skeleton stirs soon.

Star on GitHub