Welcome to promptArq! This guide will help you get started with managing your AI prompts effectively.
Live Demo (GitHub Spark): Visit: https://arqioly-prompt-atom--tamaygz.github.app/
Local Development:
git clone https://github.com/tamaygz/promptArq.git
cd promptArq
npm install
npm run dev-
Authentication (Optional but recommended for teams)
- Click "Sign in with GitHub" in the top right
- Authorize the application
- Your prompts will be saved to your account
-
Without Authentication
- All features available except team collaboration
- Prompts saved to browser localStorage
- Data persists across sessions on same device
The fundamental unit - a piece of text you use with AI models. Each prompt has:
- Title - Short, descriptive name
- Description - What the prompt does
- Content - The actual prompt text
- Tags - Labels for organization
- Project & Category - Hierarchical organization
Top-level containers for organizing related prompts. Examples:
- "Customer Support" project
- "Content Writing" project
- "Code Review" project
Subdivisions within projects. Example:
- Project: "Customer Support"
- Category: "Email Templates"
- Category: "Chat Responses"
Cross-project labels for finding prompts. Examples:
#technical#beginner-friendly#reviewed
Reusable components you can reference in prompts. Think of them as "include" statements for common instructions.
Each time you significantly change a prompt, create a new version. View history, compare versions, and revert if needed.
- Click "+ New Prompt" button (top bar)
- Enter title and description
- Select project and category
- Add tags
- Write prompt content
- Click Save or press
Ctrl+S/⌘S
- Click "Templates" button (top bar)
- Browse available templates
- Click "Use Template"
- Fill in placeholders (like
{{topic}},{{tone}}) - Template converts to prompt
- Edit and save
Popular Templates:
- Code Review
- Email Response
- Content Outline
- Technical Documentation
- Social Media Post
- Bug Report
- Click any prompt in the list
- Edit in right panel
- Save changes (Ctrl+S / ⌘S)
Versioning:
- Minor changes: Just save
- Major changes: Click "New Version"
- Add change note
- Creates version history entry
Keyboard Shortcuts:
Ctrl+S/⌘S- SaveCtrl+I/⌘I- Improve with AI (when configured)
If your prompt has placeholders like {{topic}} or {{style}}:
- Open the prompt
- Click "Fill Placeholders" button
- A dialog appears with fields for each placeholder
- Fill in the values
- Click "Execute" to generate the final prompt
- Copy the result to use with your AI tool
Placeholder Features:
- Values are remembered for next time
- Clear individual values or all at once
- Skip execution and just copy filled template
Project variables are defined once at the project level and automatically replaced in all prompts within that project. This is perfect for company names, product names, URLs, or any repeated values.
Syntax Difference:
- Manual Placeholders:
{{placeholder}}(2 braces) - You fill these each time - Project Variables:
{{{variable}}}(3 braces) - Auto-replaced from project settings
Creating Project Variables:
- Click "Projects" button (gear icon in top bar)
- Go to the "Variables" tab
- Select a project from the dropdown
- Enter variable name (e.g.,
company_name) - Enter the value (e.g.,
Acme Corporation) - Click "Add Variable"
Using Project Variables in Prompts:
Dear {{customer_name}},
Thank you for contacting {{{company_name}}}.
You can reach us at {{{support_email}}} or {{{company_phone}}}.
Best regards,
{{{company_name}}} Support Team
When you execute this prompt:
{{{company_name}}},{{{support_email}}}, and{{{company_phone}}}are automatically replaced- Only
{{customer_name}}requires manual input
Benefits:
- Consistency: Same values across all prompts in a project
- Efficiency: No need to fill repeated values
- Maintainability: Update once, affects all prompts
- Clarity: Clear distinction between fixed and variable content
Managing Variables:
- View all variables grouped by project in the Variables tab
- Delete variables by clicking the trash icon
- Variables are stored with the project and sync across devices
For prompts without placeholders:
- Open the prompt
- Click "Execute" button
- Optionally select a system prompt
- Copy the result to use with your AI tool
Prompts can be executed in two ways:
Direct Execution (default):
- Prompt content is copied directly to clipboard
- Faster, no LLM processing
- Ideal for templates, snippets, or pre-written content
- Look for standard prompts without an "LLM" badge
LLM Execution:
- Prompt is processed through LLM pipeline
- Combined with system prompts
- Can include preprocessing and transformations
- Indicated by a sparkle "LLM" badge on the prompt
To enable LLM execution:
- Open prompt editor
- Check "Execute through LLM" at the bottom
- Save the prompt
- Badge appears in prompt list
- Copy Button - Quick copy to clipboard
- Execute Dialog - Fill placeholders and preview
- Export - Download as JSON for external use
- Click "Projects" button (gear icon)
- Create new project with color
- Add categories to project
- Assign prompts to project/category
- Edit prompt
- In tags field, type and press Enter
- Tags autocomplete from existing
- Create new tags on the fly
Tag Colors: Tags automatically get colors. Same tag = same color everywhere.
- Toggle "Show Archived" to see archived prompts
- Archive from prompt menu (⋮)
- Keeps prompts but removes from active view
Search Bar:
- Real-time search
- Searches title, description, content, tags
- Case-insensitive
Project Filter:
- Dropdown in top bar
- Select "All" or specific project
- Narrows visible prompts
Tag Filter:
- Click tags in tag list (left sidebar)
- Multiple tags = AND filter
- Clear filters to show all
Combined Filtering: Project filter + Tag filter + Search = powerful organization
View History:
- Open prompt
- Scroll to "Version History" section
- See all versions with change notes
Compare Versions:
- Click "View Diff" on any version
- Side-by-side comparison
- Green = added, Red = removed
Restore Version:
- View old version
- Copy content
- Paste in current version
- Save as new version
- Click "Teams" button (top bar)
- Create new team
- Enter name and description
- Generate invite link
- Open team settings
- Click "Copy Invite Link"
- Share link with team members
- They click link and join automatically
- Shared prompt library (future)
- Comments on prompts
- User directory
- Collaborative editing (future)
- Open prompt
- Scroll to "Comments" section
- Write comment
- Submit
- Comments visible to team members
- Open prompt
- Click "Share" button
- Click "Generate Share Link"
- Copy link and share
- Click shared link
- View read-only prompt
- Click "Copy to Library" to save to your account
Share Link Features:
- Public access (no auth required)
- Read-only view
- Copy content button
- Save to your library option
What is MCP? Model Context Protocol lets AI assistants (like Claude Desktop) access your prompts directly.
Setup:
-
Mark prompts for MCP exposure:
- Edit prompt
- Toggle "Expose to MCP Server"
- Save
-
Configure Claude Desktop:
- Click "MCP Server" button (top bar)
- Review exposed prompts
- Click "Copy Configuration"
- Paste in Claude Desktop config
-
Use in Claude:
- Type
/in Claude - See your prompts as tools
- Select prompt to insert
- Type
Save AI model settings for reuse.
Create Model Config:
-
Click "Model Config" button (top bar)
-
Click "Add Configuration"
-
Enter settings:
- Name (e.g., "GPT-4 Creative")
- Provider (OpenAI, Anthropic, etc.)
- Model name
- Temperature
- Max tokens
- Top P
- Penalties
-
Save configuration
Use Model Config:
- Reference in prompts
- Export for use in API calls
- Share with team
Reusable instructions you can include in prompts.
Create System Prompt:
- Click "System Prompts" button (top bar)
- Add new system prompt
- Enter name, category, content
- Save
Use System Prompt:
- Reference in prompt content
- Include via template placeholder
- Combine multiple system prompts
Categories:
- Role definitions (e.g., "Expert Python developer")
- Output formats (e.g., "Respond in JSON")
- Constraints (e.g., "Use simple language")
Export All Prompts:
- Click profile menu (top right)
- Select "Export Data"
- Download JSON file
- Contains all prompts, projects, categories, tags
Import Prompts:
- Click profile menu
- Select "Import Data"
- Choose JSON file
- Select which items to import
- Merge or replace existing data
Export Single Prompt:
- Copy content from editor
- Use share feature for formatted export
- Be descriptive: "Code Review for Python APIs" not "Code Review 1"
- Include use case: "Email: Customer Complaint Response"
- Version in name if needed: "Blog Post Generator v3"
- Start with clear objective
- Include examples when helpful
- Specify output format
- Add constraints or requirements
- Use placeholders for variables:
{{topic}},{{style}} - Use project variables for fixed values:
{{{company_name}}},{{{product}}}
- Use project variables for company info, product names, URLs, standard terms
- Use manual placeholders for customer-specific, case-specific, or dynamic content
- Naming conventions: Use descriptive names like
company_namenotcn - Keep it simple: Don't over-use variables; only for frequently repeated values
- Test replacements: Verify variables replace correctly before sharing prompts
- One project per major domain
- Categories for subtopics
- Tags for cross-cutting concerns
- Archive outdated prompts (don't delete)
- Create version for significant changes
- Write meaningful change notes
- Keep old versions for reference
- Test new versions before replacing
- Define team purpose clearly
- Set conventions (naming, tagging)
- Comment on prompts for context
- Share best practices
- Create templates for repeated patterns
- Use meaningful placeholder names
- Test templates before sharing
- Keep templates generic enough for reuse
Ctrl+S/⌘S- Save promptCtrl+I/⌘I- Improve prompt (AI)Esc- Close editor
/- Focus searchCtrl+K/⌘K- Quick actions (future)
Ctrl+Z/⌘Z- UndoCtrl+Shift+Z/⌘Shift+Z- Redo
- Check browser localStorage quota (5-10MB limit)
- Try exporting and importing data
- Clear old/archived prompts
- Use GitHub Spark deployment for unlimited storage
- Clear browser cache
- Check OAuth configuration
- Verify redirect URLs
- Try incognito mode
- Check filters (project, tags)
- Verify "Show Archived" state
- Search is case-insensitive
- Try partial words
- Verify prompts marked "Expose to MCP"
- Check Claude Desktop configuration
- Restart Claude Desktop
- See full MCP Guide
- Reduce number of prompts displayed
- Archive old prompts
- Clear browser cache
- Disable animations (future setting)
Q: Where is my data stored? A: GitHub Spark deployment uses Spark KV store. Local deployment uses browser localStorage. All data stays client-side, no server storage.
Q: Can I use without GitHub account? A: Yes! All features work except team collaboration. Data saves to browser localStorage.
Q: Is there a mobile app? A: Not yet, but the web app is mobile-responsive. Use in mobile browser.
Q: How many prompts can I store? A: Spark deployment: unlimited. localStorage: ~5-10MB (hundreds of prompts). Export regularly as backup.
Q: Can I collaborate in real-time? A: Not yet. Currently async collaboration via comments and shared prompts. Real-time editing is planned.
Q: How do I backup my data? A: Export all data regularly via profile menu. Stores JSON file you can re-import anytime.
Q: Can I use my own AI models? A: Model configs store settings but don't execute. Use exported prompts with any AI service.
Q: Is there an API? A: Not yet. MCP integration provides similar functionality for Claude Desktop.
Q: How do I report bugs? A: Create issue on GitHub repository.
- Documentation:
/docsfolder - GitHub Issues: Bug reports and feature requests
- Discussions: Community support
- Demo Site: Try features live
- Read Architecture Guide for technical details
- See Developer Guide for contributing
- Check MCP Setup for Claude Desktop integration
- Visit Windows App for desktop version