How do I install the Kubit Researching Prior Art skill?

Run npx skillmds@latest add tomevault-io/kubit-researching-prior-art in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubit Researching Prior Art safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubit Researching Prior Art?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubit Researching Prior Art free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubit Researching Prior Art?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubit Researching Prior Art by tomevault-io

Name: Kubit Researching Prior Art
Author: tomevault-io

Kubit Researching Prior Art

Use when designing new subsystem, comparing implementation approaches, or user asks how other frameworks handle something. Use when researching Laravel, Rails, AdonisJS, Inertia.js, or similar framework patterns.

tomevault-io Updated Sep 17, 2026

File contents

Researching Prior Art for Kubit

Overview

When designing subsystems, research how established frameworks solve the same problem. Capture findings in docs/BRAINDUMP.md or the relevant RFC.

When to Use

Designing new subsystem (Auth, Validation, etc.)
User asks "how does Laravel/Rails do X?"
Comparing implementation approaches
Need to justify design decisions

Frameworks to Reference

Framework	Strong Areas
Laravel	Eloquent ORM, Queue, Mail, Auth, Blade
AdonisJS	TypeScript patterns, decorators, Lucid ORM
Rails	ActiveRecord, conventions, generators
Inertia.js	SPA protocol, React SSR, forms
Remix/Next	React SSR, data loading, routing

Research Questions

When studying a pattern:

What's the public API? (method signatures, config)
What conventions are enforced?
What's the mental model? (how users think about it)
What are the extension points?
What do users complain about? (learn from mistakes)

Capture Location

Scope	Where to capture
General philosophy	docs/BRAINDUMP.md
Specific subsystem research	Relevant RFC
Design decision	SPEC.md Decision Log

Research Template

## [Subsystem] Prior Art

### Laravel
- API: `Mail::to($user)->send(new OrderShipped($order))`
- Conventions: Mailables as classes, queued by default
- Extension: Custom transports via driver config

### AdonisJS
- API: Similar but TypeScript-native
- Conventions: Decorators for metadata

### Key Insights
- [What to adopt]
- [What to avoid]
- [Kubit-specific adaptation needed]

Common Patterns Across Frameworks

Class-based entities: Controllers, Models, Jobs, Mailables are classes Decorators/Annotations: Metadata on properties and methods Convention over configuration: Sensible defaults, override when needed Fluent APIs: Method chaining for configuration DI containers: Automatic dependency resolution

Source: aniftyco/kubit — distributed by TomeVault.

---name: kubit-researching-prior-artdescription: Use when designing new subsystem, comparing implementation approaches, or user asks how other frameworks handle something. Use when researching Laravel, Rails, AdonisJS, Inertia.js, or similar framework patterns.---# Researching Prior Art for Kubit## OverviewWhen designing subsystems, research how established frameworks solve the same problem. Capture findings in docs/BRAINDUMP.md or the relevant RFC.## When to Use- Designing new subsystem (Auth, Validation, etc.)- User asks "how does Laravel/Rails do X?"- Comparing implementation approaches- Need to justify design decisions## Frameworks to Reference| Framework | Strong Areas ||-----------|--------------|| **Laravel** | Eloquent ORM, Queue, Mail, Auth, Blade || **AdonisJS** | TypeScript patterns, decorators, Lucid ORM || **Rails** | ActiveRecord, conventions, generators || **Inertia.js** | SPA protocol, React SSR, forms || **Remix/Next** | React SSR, data loading, routing |## Research QuestionsWhen studying a pattern:1. What's the public API? (method signatures, config)2. What conventions are enforced?3. What's the mental model? (how users think about it)4. What are the extension points?5. What do users complain about? (learn from mistakes)## Capture Location| Scope | Where to capture ||-------|------------------|| General philosophy | docs/BRAINDUMP.md || Specific subsystem research | Relevant RFC || Design decision | SPEC.md Decision Log |## Research Template```markdown## [Subsystem] Prior Art### Laravel- API: `Mail::to($user)->send(new OrderShipped($order))`- Conventions: Mailables as classes, queued by default- Extension: Custom transports via driver config### AdonisJS- API: Similar but TypeScript-native- Conventions: Decorators for metadata### Key Insights- [What to adopt]- [What to avoid]- [Kubit-specific adaptation needed]```## Common Patterns Across Frameworks**Class-based entities:** Controllers, Models, Jobs, Mailables are classes**Decorators/Annotations:** Metadata on properties and methods**Convention over configuration:** Sensible defaults, override when needed**Fluent APIs:** Method chaining for configuration**DI containers:** Automatic dependency resolution---> Source: [aniftyco/kubit](https://github.com/aniftyco/kubit) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions