azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Dataforth UI push + dedup + refactor, GuruRMM roadmap evolution, Azure signing setup

Browse Source 
Dataforth (projects/dataforth-dos/):
- UI feature: row coloring + PUSH/RE-PUSH buttons + Website Status filter
- Database dedup to one row per SN (2.89M -> 469K rows, UNIQUE constraint added)
- Import logic handles FAIL -> PASS retest transition
- Refactored upload-to-api.js to render datasheets in-memory (dropped For_Web filesystem dep)
- Bulk pushed 170,984 records to Hoffman API
- Statistical sanity check: 100/100 stamped SNs verified on Hoffman

GuruRMM (projects/msp-tools/guru-rmm/):
- ROADMAP.md: added Terminology (5-tier hierarchy), Tunnel Channels Phase 2,
  Logging/Audit/Observability, Multi-tenancy, Modular Architecture,
  Protocol Versioning, Certificates sections + Decisions Log
- CONTEXT.md: hierarchy table, new anti-patterns (bootstrap sacred,
  no cross-module imports), revised next-steps priorities

Session logs for both projects.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-04-15 17:39:32 -07:00
parent eae9d7f644
commit 733d87f20e
42 changed files with 9153 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/scheduled_tasks.lock Normal file
View File

@@ -0,0 +1 @@
{"sessionId":"cfd47b51-999e-4ed8-ba99-034493914f76","pid":30732,"acquiredAt":1776026819140}

117
.claude/skills/skill-creator/SKILL.md Normal file
View File

@@ -0,0 +1,117 @@
---
name: skill-creator
description: |
Create new Claude Code custom skills and slash commands. Use when the user wants to create a new skill,
add a slash command, build a custom command, or set up a new automation. Guides through the process of
defining the skill's purpose, triggers, and implementation, then generates the proper file structure.
---
# Skill Creator
You help the user create new Claude Code custom skills and slash commands.
## Two Types of Custom Extensions
### 1. Skills (`.claude/skills/{name}/SKILL.md`)
- Rich, multi-purpose capabilities with automatic invocation triggers
- Can include supporting files (scripts, references, checklists)
- Best for: complex behaviors, design patterns, validation workflows, integrations
### 2. Slash Commands (`.claude/commands/{name}.md`)
- Simple, user-invoked commands triggered by `/{name}`
- Single markdown file with instructions
- Best for: workflows the user explicitly triggers, task automation, shortcuts
- Can accept arguments via `$ARGUMENTS`
## Creation Process
### Step 1: Gather Requirements
Ask the user:
1. **What should this skill/command do?** (core purpose)
2. **Skill or command?** Help them decide:
- If it should run automatically in response to certain actions -> **Skill**
- If the user will invoke it explicitly with `/{name}` -> **Command**
- If unsure, recommend based on the use case
3. **Name** - short, kebab-case identifier (e.g., `code-review`, `deploy-check`)
4. **When should it trigger?** (for skills: automatic triggers; for commands: typical usage)
### Step 2: Generate the Files
#### For Skills
Create `.claude/skills/{name}/SKILL.md`:
```markdown
---
name: {name}
description: |
{Detailed description. This is used for discovery/matching, so be specific about
when this skill should be invoked. Include trigger keywords and example scenarios.}
---
# {Skill Title}
{Clear instructions for what Claude should do when this skill is invoked.}
## When to Invoke
{List specific triggers - file types, actions, keywords that should activate this skill.}
## Workflow
{Step-by-step process the skill follows.}
## Guidelines
{Rules, patterns, and best practices to follow.}
```
#### For Commands
Create `.claude/commands/{name}.md`:
```markdown
---
description: {One-line description shown in command list}
---
# {Command Title}
{Instructions for what Claude should do when the user runs /{name}.}
## Arguments
If the command accepts arguments, reference them via `$ARGUMENTS`.
## Workflow
{Step-by-step process.}
```
### Step 3: Register and Validate
After creating the files:
1. Confirm the file was created in the correct location
2. Tell the user they can invoke it:
- Skills: Explain the automatic triggers or manual invocation via `/skill-name`
- Commands: Tell them to use `/{name}` or `/{name} arguments`
3. Remind them to update CLAUDE.md's Commands & Skills table if they want it documented there
## Quality Checklist
Before finalizing, verify:
- [ ] Description is detailed enough for Claude to match it to relevant situations
- [ ] Instructions are clear and actionable (Claude will follow them literally)
- [ ] The skill/command doesn't duplicate an existing one
- [ ] File is in the correct location (`.claude/skills/` or `.claude/commands/`)
- [ ] Name uses kebab-case and is concise
- [ ] For skills with auto-triggers: triggers are specific enough to avoid false positives
## Tips for Good Skills/Commands
- **Be specific in descriptions** - vague descriptions lead to missed or false invocations
- **Include examples** in the instructions so Claude understands edge cases
- **Keep scope focused** - one skill per concern, don't create mega-skills
- **Test after creation** - have the user try invoking it to verify behavior
- **Reference existing patterns** - look at `.claude/skills/` and `.claude/commands/` for examples

105
.claude/skills/stop-slop/SKILL.md Normal file
View File

@@ -0,0 +1,105 @@
---
name: stop-slop
description: |
Enforce high-quality, slop-free output in all Claude responses. MANDATORY AUTOMATIC INVOCATION:
This skill is always active. It governs how Claude writes text, code comments, commit messages,
documentation, and any other output. Detects and eliminates generic AI filler, hollow phrases,
unnecessary verbosity, and performative enthusiasm. Applies to all output — conversation, code,
docs, and generated content.
---
# Stop Slop
You are a direct, competent engineer. Write like one. Every word must earn its place.
## Always-On Rules
These rules apply to ALL output at ALL times. No exceptions.
### Banned Patterns -- Never Write These
**Performative enthusiasm and filler openers:**
- "Great question!", "Excellent point!", "That's a really interesting..."
- "Certainly!", "Absolutely!", "Of course!", "Sure thing!"
- "I'd be happy to help!", "Let me help you with that!"
- "Good news!", "Here's the exciting part..."
**Hollow transitions and hedging:**
- "It's worth noting that..." (just state it)
- "It's important to remember..." (just state it)
- "As you can see..." / "As we discussed..."
- "Basically..." / "Essentially..." / "Fundamentally..."
- "In order to..." (use "to")
- "It should be noted that..." (just note it)
- "At the end of the day..."
- "Moving forward..."
**Unnecessary meta-commentary:**
- "Let me explain..." (just explain)
- "I'll now..." / "Next, I'll..." (just do it)
- "Here's what I found..." (just show it)
- "Let me break this down..." (just break it down)
**Trailing summaries and sign-offs:**
- Restating what was just done at the end of a response
- "Let me know if you have any questions!"
- "Hope this helps!"
- "Feel free to ask if you need anything else!"
- "Happy coding!" / "Happy hacking!"
- Any variation of "don't hesitate to reach out"
**Weasel words and padding:**
- "Very", "really", "quite", "rather", "somewhat", "fairly"
- "Just" (when used as filler, not as "only")
- "Simply" (when the thing isn't simple, or as filler)
- "Actually" (at start of sentences, as filler)
- "Obviously" / "Clearly" (if it were obvious, you wouldn't say it)
**Sycophantic agreement:**
- "You're absolutely right that..."
- "That's a great approach!"
- "What a thoughtful question!"
- Praising the user's code/ideas before giving feedback
### Writing Standards
**Lead with the answer.** Don't build up to it. State the conclusion, then support it if needed.
**One sentence beats three.** If you can say it shorter, do. Compress ruthlessly.
**No preamble.** Start with the substance. Drop throat-clearing intros.
**No postamble.** End when the content ends. Don't summarize what you just said. Don't offer further help.
**Be specific.** "This fails because X" not "There might be some issues with this approach."
**Code comments: only when non-obvious.** Don't add comments that restate what the code does. Comment the *why*, not the *what*. Most code needs zero comments.
**Commit messages: state the change.** Not "This commit updates the..." -- just "Update X to handle Y."
**Error messages: state what went wrong and what to do.** Not "Oops! It looks like something went wrong."
### Calibration Examples
**Slop:**
> Great question! Let me help you with that. So basically, what's happening here is that the function is essentially trying to parse the input string. It's worth noting that this can sometimes fail if the input isn't valid JSON. I'd recommend wrapping it in a try-catch block to handle any potential errors that might occur. Let me know if you have any questions!
**Clean:**
> The function fails on invalid JSON. Wrap it in try-catch:
> ```js
> try { return JSON.parse(input); } catch { return null; }
> ```
**Slop:**
> I've successfully updated the configuration file to include the new database connection settings. The changes include adding the host, port, username, and password fields as requested. Everything should be working correctly now. Feel free to test it out and let me know if you run into any issues!
**Clean:**
> Updated the database config with the new connection settings.
### What This Skill Does NOT Do
- It does not make responses terse to the point of being unhelpful
- It does not remove necessary technical explanation
- It does not prevent friendly, human tone -- just fake enthusiasm
- It does not restrict response length when length is warranted by complexity
- Thoroughness is good. Fluff is not. Know the difference.

202
.claude/skills/theme-factory/LICENSE.txt Normal file
View File

@@ -0,0 +1,202 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

59
.claude/skills/theme-factory/SKILL.md Normal file
View File

@@ -0,0 +1,59 @@
---
name: theme-factory
description: Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
license: Complete terms in LICENSE.txt
---
# Theme Factory Skill
This skill provides a curated collection of professional font and color themes themes, each with carefully selected color palettes and font pairings. Once a theme is chosen, it can be applied to any artifact.
## Purpose
To apply consistent, professional styling to presentation slide decks, use this skill. Each theme includes:
- A cohesive color palette with hex codes
- Complementary font pairings for headers and body text
- A distinct visual identity suitable for different contexts and audiences
## Usage Instructions
To apply styling to a slide deck or other artifact:
1. **Show the theme showcase**: Display the `theme-showcase.pdf` file to allow users to see all available themes visually. Do not make any modifications to it; simply show the file for viewing.
2. **Ask for their choice**: Ask which theme to apply to the deck
3. **Wait for selection**: Get explicit confirmation about the chosen theme
4. **Apply the theme**: Once a theme has been chosen, apply the selected theme's colors and fonts to the deck/artifact
## Themes Available
The following 10 themes are available, each showcased in `theme-showcase.pdf`:
1. **Ocean Depths** - Professional and calming maritime theme
2. **Sunset Boulevard** - Warm and vibrant sunset colors
3. **Forest Canopy** - Natural and grounded earth tones
4. **Modern Minimalist** - Clean and contemporary grayscale
5. **Golden Hour** - Rich and warm autumnal palette
6. **Arctic Frost** - Cool and crisp winter-inspired theme
7. **Desert Rose** - Soft and sophisticated dusty tones
8. **Tech Innovation** - Bold and modern tech aesthetic
9. **Botanical Garden** - Fresh and organic garden colors
10. **Midnight Galaxy** - Dramatic and cosmic deep tones
## Theme Details
Each theme is defined in the `themes/` directory with complete specifications including:
- Cohesive color palette with hex codes
- Complementary font pairings for headers and body text
- Distinct visual identity suitable for different contexts and audiences
## Application Process
After a preferred theme is selected:
1. Read the corresponding theme file from the `themes/` directory
2. Apply the specified colors and fonts consistently throughout the deck
3. Ensure proper contrast and readability
4. Maintain the theme's visual identity across all slides
## Create your Own Theme
To handle cases where none of the existing themes work for an artifact, create a custom theme. Based on provided inputs, generate a new theme similar to the ones above. Give the theme a similar name describing what the font/color combinations represent. Use any basic description provided to choose appropriate colors/fonts. After generating the theme, show it for review and verification. Following that, apply the theme as described above.

BIN
.claude/skills/theme-factory/theme-showcase.pdf Normal file
View File

Binary file not shown.

19
.claude/skills/theme-factory/themes/arctic-frost.md Normal file
View File

@@ -0,0 +1,19 @@
# Arctic Frost
A cool and crisp winter-inspired theme that conveys clarity, precision, and professionalism.
## Color Palette
- **Ice Blue**: `#d4e4f7` - Light backgrounds and highlights
- **Steel Blue**: `#4a6fa5` - Primary accent color
- **Silver**: `#c0c0c0` - Metallic accent elements
- **Crisp White**: `#fafafa` - Clean backgrounds and text
## Typography
- **Headers**: DejaVu Sans Bold
- **Body Text**: DejaVu Sans
## Best Used For
Healthcare presentations, technology solutions, winter sports, clean tech, pharmaceutical content.

19
.claude/skills/theme-factory/themes/botanical-garden.md Normal file
View File

@@ -0,0 +1,19 @@
# Botanical Garden
A fresh and organic theme featuring vibrant garden-inspired colors for lively presentations.
## Color Palette
- **Fern Green**: `#4a7c59` - Rich natural green
- **Marigold**: `#f9a620` - Bright floral accent
- **Terracotta**: `#b7472a` - Earthy warm tone
- **Cream**: `#f5f3ed` - Soft neutral backgrounds
## Typography
- **Headers**: DejaVu Serif Bold
- **Body Text**: DejaVu Sans
## Best Used For
Garden centers, food presentations, farm-to-table content, botanical brands, natural products.

19
.claude/skills/theme-factory/themes/desert-rose.md Normal file
View File

@@ -0,0 +1,19 @@
# Desert Rose
A soft and sophisticated theme with dusty, muted tones perfect for elegant presentations.
## Color Palette
- **Dusty Rose**: `#d4a5a5` - Soft primary color
- **Clay**: `#b87d6d` - Earthy accent
- **Sand**: `#e8d5c4` - Warm neutral backgrounds
- **Deep Burgundy**: `#5d2e46` - Rich dark contrast
## Typography
- **Headers**: FreeSans Bold
- **Body Text**: FreeSans
## Best Used For
Fashion presentations, beauty brands, wedding planning, interior design, boutique businesses.

19
.claude/skills/theme-factory/themes/forest-canopy.md Normal file
View File

@@ -0,0 +1,19 @@
# Forest Canopy
A natural and grounded theme featuring earth tones inspired by dense forest environments.
## Color Palette
- **Forest Green**: `#2d4a2b` - Primary dark green
- **Sage**: `#7d8471` - Muted green accent
- **Olive**: `#a4ac86` - Light accent color
- **Ivory**: `#faf9f6` - Backgrounds and text
## Typography
- **Headers**: FreeSerif Bold
- **Body Text**: FreeSans
## Best Used For
Environmental presentations, sustainability reports, outdoor brands, wellness content, organic products.

19
.claude/skills/theme-factory/themes/golden-hour.md Normal file
View File

@@ -0,0 +1,19 @@
# Golden Hour
A rich and warm autumnal palette that creates an inviting and sophisticated atmosphere.
## Color Palette
- **Mustard Yellow**: `#f4a900` - Bold primary accent
- **Terracotta**: `#c1666b` - Warm secondary color
- **Warm Beige**: `#d4b896` - Neutral backgrounds
- **Chocolate Brown**: `#4a403a` - Dark text and anchors
## Typography
- **Headers**: FreeSans Bold
- **Body Text**: FreeSans
## Best Used For
Restaurant presentations, hospitality brands, fall campaigns, cozy lifestyle content, artisan products.

19
.claude/skills/theme-factory/themes/midnight-galaxy.md Normal file
View File

@@ -0,0 +1,19 @@
# Midnight Galaxy
A dramatic and cosmic theme with deep purples and mystical tones for impactful presentations.
## Color Palette
- **Deep Purple**: `#2b1e3e` - Rich dark base
- **Cosmic Blue**: `#4a4e8f` - Mystical mid-tone
- **Lavender**: `#a490c2` - Soft accent color
- **Silver**: `#e6e6fa` - Light highlights and text
## Typography
- **Headers**: FreeSans Bold
- **Body Text**: FreeSans
## Best Used For
Entertainment industry, gaming presentations, nightlife venues, luxury brands, creative agencies.

19
.claude/skills/theme-factory/themes/modern-minimalist.md Normal file
View File

@@ -0,0 +1,19 @@
# Modern Minimalist
A clean and contemporary theme with a sophisticated grayscale palette for maximum versatility.
## Color Palette
- **Charcoal**: `#36454f` - Primary dark color
- **Slate Gray**: `#708090` - Medium gray for accents
- **Light Gray**: `#d3d3d3` - Backgrounds and dividers
- **White**: `#ffffff` - Text and clean backgrounds
## Typography
- **Headers**: DejaVu Sans Bold
- **Body Text**: DejaVu Sans
## Best Used For
Tech presentations, architecture portfolios, design showcases, modern business proposals, data visualization.

19
.claude/skills/theme-factory/themes/ocean-depths.md Normal file
View File

@@ -0,0 +1,19 @@
# Ocean Depths
A professional and calming maritime theme that evokes the serenity of deep ocean waters.
## Color Palette
- **Deep Navy**: `#1a2332` - Primary background color
- **Teal**: `#2d8b8b` - Accent color for highlights and emphasis
- **Seafoam**: `#a8dadc` - Secondary accent for lighter elements
- **Cream**: `#f1faee` - Text and light backgrounds
## Typography
- **Headers**: DejaVu Sans Bold
- **Body Text**: DejaVu Sans
## Best Used For
Corporate presentations, financial reports, professional consulting decks, trust-building content.

19
.claude/skills/theme-factory/themes/sunset-boulevard.md Normal file
View File

@@ -0,0 +1,19 @@
# Sunset Boulevard
A warm and vibrant theme inspired by golden hour sunsets, perfect for energetic and creative presentations.
## Color Palette
- **Burnt Orange**: `#e76f51` - Primary accent color
- **Coral**: `#f4a261` - Secondary warm accent
- **Warm Sand**: `#e9c46a` - Highlighting and backgrounds
- **Deep Purple**: `#264653` - Dark contrast and text
## Typography
- **Headers**: DejaVu Serif Bold
- **Body Text**: DejaVu Sans
## Best Used For
Creative pitches, marketing presentations, lifestyle brands, event promotions, inspirational content.

19
.claude/skills/theme-factory/themes/tech-innovation.md Normal file
View File

@@ -0,0 +1,19 @@
# Tech Innovation
A bold and modern theme with high-contrast colors perfect for cutting-edge technology presentations.
## Color Palette
- **Electric Blue**: `#0066ff` - Vibrant primary accent
- **Neon Cyan**: `#00ffff` - Bright highlight color
- **Dark Gray**: `#1e1e1e` - Deep backgrounds
- **White**: `#ffffff` - Clean text and contrast
## Typography
- **Headers**: DejaVu Sans Bold
- **Body Text**: DejaVu Sans
## Best Used For
Tech startups, software launches, innovation showcases, AI/ML presentations, digital transformation content.