grace-init

Name: grace-init
Author: osovv

github.com/osovvDevelopment25640 installsUpdated 5w ago

About grace-init

grace-init bootstraps a GRACE 4 project by creating its canonical context, graph, verification, and change directories from templates. It is for projects adopting GRACE and avoids overwriting existing artifacts without confirmation.

Key features

01Create canonical GRACE 4 files
02Populate XML files from templates
03Create context, graph, and verification layouts
04Avoid overwriting without confirmation
05Validate with grace lint when available

Use cases

01Initialize GRACE structure in a project
02Add context and verification templates
03Set up active and archived change directories

MCP support

This skill initializes project artifacts for use with GRACE, including graph, verification, and change directories. It recommends validating the setup with the GRACE CLI when available.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/osovv/grace-marketplace --skill grace-init

After installing, type/grace-initin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/

openai.yaml

assets/

AGENTS.md.template

assets/.grace/context/

deployment.xml.template

principles.xml.template

requirements.xml.template

technology.xml.template

ux-guidelines.xml.template

assets/.grace/graph/

index.xml.template

main.xml.template

assets/.grace/verification/

index.xml.template

main.xml.template

Details

From the project README

Create the canonical GRACE 4 project layout from this skill's `assets/` templates:

AGENTS.md
.grace/context/requirements.xml
.grace/context/technology.xml
.grace/context/principles.xml
.grace/context/deployment.xml
.grace/context/ux-guidelines.xml
.grace/graph/index.xml
.grace/graph/main.xml
.grace/verification/index.xml
.grace/verification/main.xml
.grace/changes/active/
.grace/changes/archive/

Every XML artifact uses graceVersion="4.0". Semantic anchors are XML tags, never attributes. Do not create dummy C-* change bundles. Do not overwrite existing .grace artifacts without explicit confirmation.

<template_sources>

Template source	Target in project
`assets/AGENTS.md.template`	`AGENTS.md`
`assets/.grace/context/requirements.xml.template`	`.grace/context/requirements.xml`
`assets/.grace/context/technology.xml.template`	`.grace/context/technology.xml`
`assets/.grace/context/principles.xml.template`	`.grace/context/principles.xml`
`assets/.grace/context/deployment.xml.template`	`.grace/context/deployment.xml`
`assets/.grace/context/ux-guidelines.xml.template`	`.grace/context/ux-guidelines.xml`
`assets/.grace/graph/index.xml.template`	`.grace/graph/index.xml`
`assets/.grace/graph/main.xml.template`	`.grace/graph/main.xml`
`assets/.grace/verification/index.xml.template`	`.grace/verification/index.xml`
`assets/.grace/verification/main.xml.template`	`.grace/verification/main.xml`
</template_sources>

1. Gather project name, annotation, keywords, language/runtime/framework, testing stack, observability constraints, deployment applicability, UX applicability, and any known initial modules. 2. If `.grace` or `AGENTS.md` already exists, stop and ask whether to keep, merge, or overwrite each existing artifact. Never overwrite silently. 3. Create `.grace/context`, `.grace/graph`, `.grace/verification`, `.grace/changes/active`, and `.grace/changes/archive`. 4. Read each `.template` file, replace `$PLACEHOLDER` values with gathered project information, and write the target file. 5. Print created files and recommend the next workflow: use `grace-spec` to create an active `GraceChangeSpec`, then `grace-plan` to produce a `GraceChangePlan` before implementation.

<hard_rules>

GRACE 4 state lives under .grace; do not create legacy docs/*.xml as the bootstrap surface.
GraceChangeSpec and GraceChangePlan are created by later change workflows, not by init.
If legacy GRACE 3 docs are present, explain that migration is handled only by grace-migrate; init must not convert or delete them.
Validate the resulting project with grace lint --path <project-root> when the CLI is available. </hard_rules>

Comments

Markdown supported

Details

Author: osovv
Repository: osovv/grace-marketplace
Category: Development
Installs: 40
GitHub stars: 256

Report

More skills

All skills

remotion-render

github.com/inference-sh

1.6M

Render videos from React/Remotion component code via inference.sh. Pass TSX code, get MP4. Supports all Remotion APIs: useCurrentFrame, useVideoConfig, spring, interpolate, AbsoluteFill, Sequence. Configurable resolution, FPS, duration, codec. Use for: programmatic video generation, animated graphics, motion design, data-driven videos, React animations to video. Triggers: remotion, render video from code, tsx to video, react video, programmatic video, remotion render, code to video, animated video, motion graphics code, react animation video

improve-codebase-architecture

github.com/mattpocock

1.2M

Scan a codebase for architecture improvement opportunities, present them as a visual HTML report, then dive deep into whichever one you pick.

design-mobile-apps

github.com/designed-by-ai

1.1M

Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML

vercel-react-best-practices

github.com/vercel-labs

848.6k

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.