firstspirit-fs-cli

Automate FirstSpirit template export, modification, and re-import via fs-cli workflows.

Updated Oct 30, 2025
One-click install
npx skills add https://github.com/rawe/claude-dev-skills --skill firstspirit-fs-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firstspirit-fs-cli
Source: https://github.com/rawe/claude-dev-skills/tree/main/firstspirit-fs-cli
Command: npx skills add https://github.com/rawe/claude-dev-skills --skill firstspirit-fs-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Java 17+, curl/wget, fs-cli, fs-isolated-runtime.jar, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manual FirstSpirit CMS template development is complex, error-prone, and time-consuming, especially synchronizing changes between local and server environments. This skill automates the setup, export, modification, and import of templates, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Automated Setup & Configuration: Guides through fs-cli installation, environment setup, and .env file creation.
  • Seamless Template Synchronization: Export templates from FirstSpirit server to a local sync_dir/ and import modified templates back.
  • Intelligent Template Modification: Provides knowledge on template structure, file types, and best practices for editing StoreElement.xml or GomSource.xml files.
  • Use Case: A developer needs to update a page template. Instead of manual server access, they use this skill to export the template, modify its GomSource.xml locally with Claude Code, and then import the changes back to the server, all while ensuring correct syntax and structure.

Quick Start

Guide me through setting up the fs-cli environment for my FirstSpirit project. Once set up, export all page templates from the server to my local sync_dir/.

Frequently Asked Questions about firstspirit-fs-cli

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

FAQPage Schema
How do I automate FirstSpirit template synchronization between local and server environments?

Template synchronization automates export, modification, and re-import workflows using fs-cli. Export templates from your FirstSpirit server to a local directory, edit files like StoreElement.xml or GomSource.xml locally, then import changes back to sync server state—eliminating manual, error-prone updates.

What are the prerequisites for setting up fs-cli for FirstSpirit template development?

Set up requires Java 17+, curl or wget, fs-cli installation, and fs-isolated-runtime.jar. These dependencies enable environment configuration, template export/import operations, and proper isolation for template processing in your FirstSpirit development workflow.

Can I use fs-cli to export and modify FirstSpirit templates without server access each time?

Yes. Export templates once to a local sync directory, then edit template files offline with proper syntax knowledge. Batch modifications and re-import after verification—reducing repeated server access and enabling test-driven template development workflows.

What's the correct workflow for safely importing modified FirstSpirit templates back to the server?

Follow export-before-modify-verify-import: export templates first as a baseline, edit locally with template structure knowledge, verify syntax and changes match requirements, then import to resync. This test-driven approach prevents syntax errors and ensures consistency between environments.

Do I need deep knowledge of FirstSpirit template structure to use fs-cli automation?

Yes. Understanding template file types, StoreElement.xml and GomSource.xml structure, and template syntax is required for safe editing and re-import. The skill provides guidance on structure and best practices to support proper template modification workflows.

Why is template synchronization automation better than manual FirstSpirit CMS development?

Manual template updates across local and server environments are time-consuming and error-prone. Automation via fs-cli reduces manual effort, ensures consistency, supports repeatability, and enables test-driven workflows—critical for complex CMS development at scale.