deckbuilder 1.0.0b1__tar.gz

deckbuilder-1.0.0b1/CLAUDE.md

@@ -0,0 +1,317 @@
+# CLAUDE.md
+
+## Project Overview
+
+Deckbuilder is a Python library and accompanying MCP (Model Context Protocol) Server for intelligent PowerPoint presentation generation.
+The project has evolved beyond initial setup into a comprehensive content-first presentation intelligence system.
+
+### 🔄 Project Awareness & Context
+- **Always read `PLANNING.md`** at the start of a new conversation to understand the project's architecture, goals, style, and constraints.
+- **Check `TASK.md`** before starting a new task. If the task isn’t listed, add it with a brief description and today's date.
+- **Use consistent naming conventions, file structure, and architecture patterns** as described in `PLANNING.md`.
+
+### 🧱 Code Structure & Modularity
+- **Never create a file longer than 500 lines of code.** If a file approaches this limit, refactor by splitting it into modules or helper files.
+- **Organize code into clearly separated modules**, grouped by feature or responsibility.
+- **Use clear, consistent imports** (prefer relative imports within packages).
+
+### 🧪 Testing & Reliability
+- **Always create Pytest unit tests for new features** (functions, classes, routes, etc).
+- **After updating any logic**, check whether existing unit tests need to be updated. If so, do it.
+- **Tests should live in a `/tests` folder** mirroring the main app structure.
+  - Include at least:
+    - 1 test for expected use
+    - 1 edge case
+    - 1 failure case
+
+### ✅ Task Completion
+- **Mark completed tasks in `TASK.md`** immediately after finishing them.
+- Add new sub-tasks or TODOs discovered during development to `TASK.md` under a “Discovered During Work” section.
+
+### 📎 Style & Conventions
+- **Use Python** as the primary language.
+- **Follow PEP8**, use type hints, and format with `black`.
+- **Run flake8**, and fix any errors before check-in.
+- **Use `pydantic` for data validation**.
+
+
+## 🔧 Code Quality Standards
+
+**CRITICAL: Always run these commands and fix ALL errors before committing:**
+
+```bash
+# Format code with black (REQUIRED)
+black --line-length 100 src/
+
+# Check all flake8 violations (REQUIRED)
+flake8 src/ tests/ --max-line-length=100 --ignore=E203,W503,E501
+
+# Run tests to ensure no regressions (REQUIRED)
+pytest tests/
+```
+
+**⚠️ ZERO TOLERANCE POLICY: No commits allowed with flake8 F-level errors (F401, F841, F811, F541, etc.)**
+
+
+
+
+### Code Quality Rules
+
+**Imports (Critical F-level violations):**
+- Remove ALL unused imports (F401) - check each import statement
+- Import order: stdlib → third-party → local, alphabetical within groups
+- Use `# noqa: E402` only when imports must follow `sys.path.insert()`
+- Never duplicate imports (F811)
+
+**Variables (Critical F-level violations):**
+- Remove ALL unused variables (F841) - either use them or delete them
+- Use `_` for intentionally unused variables: `for _, item in enumerate(items)`
+- Comment out variables for future use: `# content_length = len(content)  # Future: use for analysis`
+
+**F-strings (Critical F-level violations):**
+- Fix ALL f-strings without placeholders (F541): `f"Hello"` → `"Hello"`
+- Only use f-strings when you have variables: `f"Hello {name}"`
+
+**Line Length (E501 - Style violations):**
+- Maximum 100 characters per line (ignored in CI for now)
+- Break long function calls, docstrings, and string literals when practical
+- Use parentheses for continuation: `("long string part 1 "\n"part 2")`
+- **Note**: E501 ignored in CI to focus on critical F-level errors first
+
+### Enforcement Strategy
+1. **Pre-commit**: Always run `flake8` before any commit
+2. **Zero F-errors**: F-level errors MUST be fixed immediately
+3. **Style consistency**: Use `black` for automatic formatting
+4. **Test coverage**: Ensure all code changes include relevant tests
+
+### CI Integration
+The project includes GitHub Actions workflows that enforce code quality:
+
+- **`.github/workflows/test.yml`**: Runs pytest and flake8 on every push/PR
+- **`.github/workflows/claude-code-review.yml`**: Claude-powered code review for PRs
+
+**CI Requirements:**
+- All tests must pass (50+ tests including engine, template processing, etc.)
+- Zero flake8 F-level errors (F401, F841, F811, F541)
+- Python 3.11+ compatibility required
+
+
+
+**Current Status**:
+- ✅ Core presentation engine implemented with structured frontmatter support
+- ✅ Template system with semantic detection and JSON mapping
+- 🚧 Content-first MCP tools in design phase
+- 📋 50+ layout templates planned for progressive implementation
+
+## Architecture
+
+Deckbuilder implements a **content-first design philosophy** with three key components:
+1. **Presentation Engine**: PowerPoint generation with template support
+2. **Content Intelligence**: Semantic analysis for layout recommendations
+3. **Progressive Templates**: Expanding library of business presentation layouts
+
+The system transforms LLMs from layout pickers into intelligent presentation consultants.
+
+## Development Environment
+
+Always use Python 3.11+ and activate the virtual environment:
+```bash
+source .venv/bin/activate
+```
+
+## ⚠️ IMPORTANT: MCP Server Environment Configuration
+
+**When testing the engine directly (not through MCP)**, the presentation engine will fail to load template mappings because environment variables are not set. Environment variables are configured in the MCP server parameters, not in local `.env` files.
+
+**MCP Server Configuration** (Claude Desktop config):
+```json
+{
+  "env": {
+    "DECK_TEMPLATE_FOLDER": "/path/to/deckbuilder/assets/templates",
+    "DECK_OUTPUT_FOLDER": "/path/to/deckbuilder/output",
+    "DECK_TEMPLATE_NAME": "default"
+  }
+}
+```
+
+**Impact on Development**:
+- ✅ **MCP tools work correctly** - environment variables are available
+- ❌ **Direct engine testing may fail** - missing template paths cause fallback to minimal layout mapping
+- ❌ **Layout selection issues** - incorrect layouts selected when template mapping not loaded
+
+**Testing Workaround**: When testing engine directly, manually set environment variables or expect fallback behavior with limited layouts.
+
+## Design Approach
+
+# How you work
+1. Design a feature first, remind me to put you into plan-only mode
+2. Save that design into ./docs/Features/feature_name.md
+3. At the bottom of the design put a TODO which you implement as we go.
+
+This project follows a **content-first methodology**:
+1. **Understand user content and communication goals first**
+2. **Recommend presentation structure based on message intent**
+3. **Suggest optimal layouts with audience consideration**
+4. **Optimize content for chosen layouts**
+
+Never start with "what layouts exist?" - always start with "what does the user want to communicate?"
+
+## Key Design Decisions
+
+### Content Intelligence Storage
+- **Decision**: Separate `layout_intelligence.json` file (Option 2)
+- **Rationale**: Clean separation of technical template structure from semantic content intelligence
+- **Location**: `src/layout_intelligence.json`
+- **Integration**: Used by content-first MCP tools for layout recommendations
+
+### Template Architecture
+- **Technical Structure**: `default.json` (placeholder mappings)
+- **Semantic Intelligence**: `layout_intelligence.json` (content matching)
+- **Documentation**: `SupportedTemplates.md` (implementation roadmap)
+- **Hybrid Approach**: Semantic detection + JSON mapping for reliable content placement
+
+## Feature Documentation
+
+Refer to these comprehensive specifications before implementing:
+
+### Core Feature Specifications
+- **[Placeholder_Matching.md](docs/Features/Placeholder_Matching.md)**:
+  - Hybrid semantic detection and JSON mapping system
+  - Template analyzer workflow and JSON schema
+  - Content placement strategies and troubleshooting
+  - **Content Intelligence Storage Design** with Option 2 decision rationale
+
+- **[Template_Discovery.md](docs/Features/Template_Discovery.md)**:
+  - Content-first MCP tools design (analyze_presentation_needs, recommend_slide_approach, optimize_content_for_layout)
+  - Complete end-to-end user workflow scenarios
+  - Design evolution from layout-centric to content-first approach
+  - Implementation roadmap and success criteria
+
+- **[Supported_Templates.md](docs/Features/Supported_Templates.md)**:
+  - Progressive implementation roadmap for 50+ business presentation layouts
+  - Status tracking with ✅/❌ indicators across 7 layout categories
+  - Required placeholders and descriptions for each layout
+  - Current: 12 implemented, 50+ planned
+
+## Implementation Priorities
+
+### Phase 1: Content-First MCP Tools ✅ COMPLETED
+1. ✅ `analyze_presentation_needs()` - Content and goal analysis (placeholder implemented)
+2. ✅ `recommend_slide_approach()` - Layout recommendations (placeholder implemented)
+3. ✅ `optimize_content_for_layout()` - Content optimization and YAML generation (placeholder implemented)
+
+### Phase 2: Template Management System ✅ COMPLETED
+1. ✅ **CLI Template Management Tools** - Comprehensive command-line utilities
+   - `analyze` - Template structure analysis with detailed validation
+   - `document` - Auto-generated comprehensive template documentation
+   - `validate` - Template and mapping validation with specific fix suggestions
+   - `enhance` - Master slide placeholder modification with organized backup system
+2. ✅ **Master Slide Enhancement** - Direct PowerPoint template modification using python-pptx
+3. ✅ **Organized File Management** - `.g.pptx` convention and dedicated backup folders
+4. ✅ **Comprehensive Documentation** - Updated user guides and technical specifications
+
+### Phase 3: Content Intelligence & Layout Expansion (Current Focus)
+1. **Convention-Based Naming System** - Standardized placeholder naming patterns
+2. **Layout Intelligence Implementation** - `src/layout_intelligence.json` with semantic metadata
+3. **Content Matching Algorithms** - Smart layout recommendations based on content analysis
+4. **Template Library Expansion** - Progressive implementation of 50+ layouts from `SupportedTemplates.md`
+5. **Performance Optimization** - Enhanced content intelligence and comprehensive testing
+
+## Important Instructions
+
+1. **🔧 CODE QUALITY FIRST**: Always run `flake8` and fix ALL F-level errors before any commit
+2. **Always design a feature first, and ask me to review the design before implementing it**
+3. **Follow content-first principles**: Start with user needs, not system capabilities
+4. **Maintain separation of concerns**: Technical structure vs semantic intelligence
+5. **Document decisions**: Update feature docs when making design choices
+6. **Test with real scenarios**: Use actual user presentation needs for validation
+7. **Clean imports**: Remove unused imports (F401) and variables (F841) immediately
+8. **Format consistently**: Use `black --line-length 100 src/` before committing
+9. **🚫 NO ROOT DIRECTORY POLLUTION**: Never create test files, output files, or temporary files in the root directory. Use appropriate subdirectories:
+   - Test files: `/tests/` directory with proper structure
+   - Output files: `/tests/output/` directory ONLY
+   - Temporary files: Use Python's `tempfile` module or existing `/temp/` subdirectories
+   - Integration tests: `/tests/integration/` directory
+   - Debug scripts: `/tests/debug/` directory (temporary, must be cleaned up)
+   - **NEVER create new directories in root** - use existing structure only
+
+## Testing & Validation
+
+When tests fail, ask the user how to fix them before actually fixing them.
+
+### Test Files and Usage
+
+The project includes comprehensive test files for validation:
+
+#### Core Test Files
+- **`tests/test_presentation.md`**: Primary markdown test with structured frontmatter examples
+  - Tests Four Columns, Two Content, Comparison, and Picture with Caption layouts
+  - Demonstrates clean YAML syntax and content optimization
+  - Used for end-to-end presentation generation testing
+
+- **`tests/test_structured_frontmatter.md`**: Extended structured frontmatter examples
+  - Additional layout variations and edge cases
+  - Content formatting and validation scenarios
+
+- **`tests/FormattingTest.md`**: Inline formatting validation
+  - Bold, italic, underline combinations
+  - Complex formatting patterns and edge cases
+
+- **`tests/TestPrompt.md`**: User scenario testing
+  - Real-world presentation requests
+  - Content-first workflow validation
+
+#### Template Management CLI Tools
+- **`src/deckbuilder/cli_tools.py`**: Comprehensive template management utilities
+  - Extracts PowerPoint template structure with detailed validation
+  - Generates JSON mappings and comprehensive documentation
+  - Enhances templates with master slide placeholder modification
+  - Provides organized backup system and error reporting
+
+### Running Tests
+
+#### Template Analysis and Enhancement
+Generate JSON mappings and enhance PowerPoint templates:
+```bash
+# Analyze template structure with validation
+python src/deckbuilder/cli_tools.py analyze default --verbose
+
+# Generate comprehensive documentation
+python src/deckbuilder/cli_tools.py document default
+
+# Validate template and mappings
+python src/deckbuilder/cli_tools.py validate default
+
+# Enhance template with corrected placeholder names
+python src/deckbuilder/cli_tools.py enhance default
+```
+
+#### Presentation Generation Testing
+Test structured frontmatter system:
+```bash
+# Through MCP client (Claude Desktop)
+# Use create_presentation_from_markdown tool with test_presentation.md content
+```
+
+#### Manual Validation
+1. **Content Placement**: Verify titles, content, and placeholders appear correctly
+2. **Formatting**: Check bold, italic, underline rendering
+3. **Layout Accuracy**: Ensure structured frontmatter maps to correct layouts
+4. **Template Loading**: Verify JSON mappings work with PowerPoint templates
+
+### Test Data Validation
+
+The test files validate:
+- **Structured frontmatter conversion**: YAML → JSON → PowerPoint
+- **Content optimization**: 64% complexity reduction achieved
+- **Layout intelligence**: Semantic content matching
+- **Formatting preservation**: All inline formatting maintained
+- **Template compatibility**: Works across different PowerPoint templates
+
+### Output Validation
+
+Generated presentations should demonstrate:
+- Clean content placement without formatting explosion
+- Proper layout selection based on content structure
+- Accurate placeholder mapping using semantic detection + JSON fallback
+- Professional appearance matching structured frontmatter specifications

deckbuilder-1.0.0b1/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2025 Bruce McLeod
+
+   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.

deckbuilder-1.0.0b1/MANIFEST.in

@@ -0,0 +1,63 @@
+# Include project metadata files
+include README.md
+include LICENSE
+include CLAUDE.md
+include PLANNING.md
+include TASK.md
+
+# Include requirements and configuration
+include requirements.txt
+include pyproject.toml
+include pytest.ini
+include bandit.yaml
+include deckbuilder-completion.bash
+
+# Include PlaceKitten image assets
+recursive-include src/placekitten/images *.png *.jpg *.jpeg
+include src/placekitten/README.md
+
+# Include template assets
+recursive-include assets/templates *.pptx *.json
+
+# Include layout intelligence data
+include src/deckbuilder/layout_intelligence.json
+
+# Include documentation
+recursive-include docs *.md *.css *.html
+
+# Include examples (will create these)
+recursive-include examples *.md *.json
+
+# Include test data and fixtures (needed for some functionality)
+recursive-include tests/deckbuilder/fixtures *.json *.md
+include tests/deckbuilder/test_presentation.md
+include tests/deckbuilder/test_presentation.json
+
+# Exclude unnecessary files
+global-exclude *.pyc
+global-exclude *.pyo
+global-exclude *.pyd
+global-exclude __pycache__
+global-exclude .pytest_cache
+global-exclude .coverage
+global-exclude *.egg-info
+global-exclude .DS_Store
+global-exclude Thumbs.db
+
+# Exclude development files
+global-exclude .git*
+global-exclude .vscode
+global-exclude .idea
+exclude .gitignore
+exclude .pre-commit-config.yaml
+
+# Exclude output and temporary directories
+recursive-exclude output *
+recursive-exclude temp *
+recursive-exclude template_output *
+recursive-exclude tests/deckbuilder/output *
+recursive-exclude tests/placekitten/test_output *
+
+# Exclude build artifacts
+recursive-exclude dist *
+recursive-exclude build *