skills.rest
Common Tools avatar

Common Tools

Official

@commontoolsinc

0Followers
|
12Public Repos
|
5Published Skills

A new fabric for computing.

🐙 GitHub ↗🌐 Website ↗🐤 @CommonTools ↗
Skills Distribution
DomainDeveloper To...Component Architec.. (30%)Deployment Orchest.. (30%)Knowledge Management (20%)Project Tracking (20%)

Agent Skills by Common Tools

Showing 5 vetted skills indexed across 1 GitHub repositories.

commontoolsinccommontoolsinc
37

knowledge-base

Resolve documentation, code, and spec conflicts using a defined source hierarchy.

Official
Basic
commontoolsinccommontoolsinc
37

task-management

Break down plans into subtasks and track progress using beads (bd).

Official
Intermediate
commontoolsinccommontoolsinc
37

pattern-dev

Create and debug CommonTools patterns with ct CLI tooling.

Official
Advanced
commontoolsinccommontoolsinc
37

ct

Automate charm deployment and management using the ct CLI.

Official
Intermediate
commontoolsinccommontoolsinc
37

lit-component

Build theme-aware Lit components with Cell integration for Common UI v2.

Official
Advanced

Frequently Asked Questions About Common Tools

FAQPage Schema
What specific tasks can be performed using Common Tools?▼

Common Tools enables the creation of theme-aware interface components, the deployment and management of charms, and the resolution of technical documentation conflicts. Additionally, it provides a mechanism for decomposing project plans into granular subtasks for progress monitoring.

Which technical personas benefit most from these capabilities?▼

Frontend engineers building UI components, DevOps engineers managing charm-based deployments, and technical leads responsible for maintaining documentation integrity and project tracking benefit from these capabilities. The ecosystem is designed for teams requiring structured development and deployment governance.

What are the prerequisites for implementing Common Tools?▼

Implementation requires familiarity with the Common Tools environment, specifically the ct and bd interfaces. Users must have a configured source hierarchy for documentation resolution and an existing Lit-based project structure to utilize the component integration features effectively.