ctforms

Extract and structure metadata from ChurchTools extension projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ct-mg/CT-Forms --skill ctforms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctforms
Source: https://github.com/ct-mg/CT-Forms/tree/main
Command: npx skills add https://github.com/ct-mg/CT-Forms --skill ctforms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ctforms project addresses the complexity of building and maintaining conditional group registration forms inside ChurchTools by providing a Vue 3-based extension framework with a robust KV store, multi-extension architecture, and phased feature development.

Core Features & Use Cases

  • Unified extension model: A modular extension with separate main and admin entry points, backed by a key-value store for persistence.
  • Phase-driven development: Clear roadmap from basic form management to a full Form Builder and branching logic.
  • Developer-friendly docs: Extensive docs for setup, architecture, and troubleshooting to accelerate onboarding and maintenance.

Quick Start

Install dependencies, boot the dev server on port 5174, and deploy extensions via ChurchTools deployment workflow as documented.

Frequently Asked Questions about ctforms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build conditional registration forms in ChurchTools?

You can build conditional registration forms in ChurchTools using a Vue 3-based extension framework with a key-value store for persistence and multi-phase development supporting branching logic and a full Form Builder.

What is the best way to document a ChurchTools extension project?

Documenting a ChurchTools extension project involves extracting metadata from SKILL.md frontmatter and YAML-based descriptions, then structuring fields for discovery, risk assessment, and governance to enable rapid onboarding.

Does the ChurchTools forms extension support separate admin and main entry points?

Yes, the ChurchTools forms extension uses a modular architecture with separate main and admin entry points, backed by a key-value store to manage persistence across the different extension interfaces.

How do I set up a Vue 3 extension for ChurchTools forms?

To set up a Vue 3 extension for ChurchTools forms, install dependencies, boot the development server on port 5174, and deploy extensions via the documented ChurchTools deployment workflow.

Can I use a KV store for state persistence in ChurchTools extensions?

Yes, you can use a key-value store for state persistence in ChurchTools extensions, providing robust data management for conditional group registration forms and multi-extension architectures.

What are the limitations of building forms with ChurchTools extensions?

Building forms with ChurchTools extensions requires adherence to a phased development roadmap, currently targeting basic form management before advancing to a full Form Builder and complex branching logic capabilities.