asc-appstore-tools 0.1.28__tar.gz

asc_appstore_tools-0.1.28/.agents/skills/frontend-design/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill for UI tasks that build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+Use this skill to design and implement bold, production-ready frontends when the request involves UI. Combine it with repository UI/UX requirements (`docs/ui/requirements.md`) and existing design systems.
+
+## Design Thinking
+
+Before coding, lock in a clear, memorable direction:
+- **Purpose**: What problem does the interface solve? Who uses it?
+- **Tone**: Commit to a strong aesthetic (e.g., brutalist/raw, retro-futuristic, editorial/magazine, luxury/refined, playful/toy-like, industrial/utilitarian). Choose one and execute it precisely.
+- **Constraints**: Framework, performance, accessibility, build tooling.
+- **Differentiation**: What makes this unforgettable? Aim for a single standout idea.
+
+Then build working code (HTML/CSS/JS, React, templ, etc.) that is:
+- Production-grade and functional
+- Visually striking with a cohesive point of view
+- Meticulous in spacing, motion, and detail
+
+## Frontend Aesthetics Guidelines
+
+- **Typography**: Pick characterful, non-default fonts; pair a distinctive display font with a refined body font. Avoid Arial/Inter/Roboto/system defaults.
+- **Color & Theme**: Define a strong palette with CSS variables; prefer decisive dominance + accents over timid mixes.
+- **Motion**: Use meaningful animations (page load, staggered reveals, purposeful hover states). Prefer CSS; keep motion aligned to the chosen aesthetic.
+- **Spatial Composition**: Consider asymmetry, overlap, generous negative space or intentional density. Avoid cookie-cutter layouts.
+- **Background & Details**: Build atmosphere with gradients, meshes, textures, layered transparencies, dramatic shadows, decorative borders, custom cursors, or grain overlays—matching the aesthetic.
+
+Avoid generic AI-looking designs (purple-on-white defaults, predictable layouts, overused fonts, interchangeable components). Each UI should feel intentionally crafted for its context. Match implementation effort to the chosen style: maximalism demands rich effects; minimalism demands precise restraint.

asc_appstore_tools-0.1.28/.cursor/mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "tdesign-mcp-server": {
+      "command": "npx",
+      "args": ["-y", "tdesign-mcp-server@latest"]
+    }
+  }
+}

asc_appstore_tools-0.1.28/.github/workflows/ci.yml

@@ -0,0 +1,47 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.9", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package
+        run: pip install -e ".[dev]"
+
+      - name: Check package version alignment
+        run: pytest tests/test_project_dependencies.py::test_package_version_matches_cli_version -q
+
+      - name: Run tests
+        run: pytest -q -m "not e2e"
+
+  frontend:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: npm
+          cache-dependency-path: frontend/package-lock.json
+
+      - name: Install and build SPA
+        working-directory: frontend
+        run: |
+          npm ci
+          npm run build

asc_appstore_tools-0.1.28/.github/workflows/publish.yml

@@ -0,0 +1,32 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: pip install build twine
+
+      - name: Build package
+        run: python -m build
+
+      - name: Publish to PyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+        run: twine upload dist/*

asc_appstore_tools-0.1.28/.gitignore

@@ -0,0 +1,13 @@
+config/.env
+config/*.p8
+__pycache__/
+*.pyc
+.DS_Store
+.asc/
+*.egg-info/
+dist/
+build/
+.worktrees/
+docs/superpowers/
+.superpowers/
+frontend/node_modules/

asc_appstore_tools-0.1.28/.gitlab-ci.yml

@@ -0,0 +1,21 @@
+stages:
+  - test
+
+variables:
+  PIP_DISABLE_PIP_VERSION_CHECK: "1"
+
+pytest:
+  stage: test
+  image: python:3.12-bookworm
+  script:
+    - pip install -e ".[dev]"
+    - pytest tests/test_project_dependencies.py::test_package_version_matches_cli_version -q
+    - pytest -q -m "not e2e"
+
+frontend:
+  stage: test
+  image: node:20-bookworm
+  script:
+    - cd frontend
+    - npm ci
+    - npm run build

asc_appstore_tools-0.1.28/AGENTS.md

@@ -0,0 +1,52 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+
+This repository is a Python CLI package for App Store Connect automation. Source code lives in `src/asc/`, with Typer CLI wiring in `cli.py`, API access in `api.py`, configuration in `config.py`, and feature commands under `src/asc/commands/`. Template upload data lives in `src/asc/templates/`. Tests are in `tests/` and mirror feature areas with files such as `test_api.py`, `test_metadata.py`, and `test_build.py`. Example user data and screenshots are under `data/`; tutorials and architecture notes are in `docs/` and `ARCHITECTURE.md`.
+
+## Build, Test, and Development Commands
+
+Install the package for local development:
+
+```bash
+pip install -e ".[dev]"
+```
+
+Run the test suite:
+
+```bash
+pytest
+```
+
+Build distributable packages:
+
+```bash
+python -m build
+```
+
+Run the CLI locally after editable install:
+
+```bash
+asc --help
+asc --app myapp upload --dry-run
+```
+
+Publishing is handled by `.github/workflows/publish.yml` when a `v*.*.*` tag is pushed.
+
+## Coding Style & Naming Conventions
+
+Use Python 3.9+ syntax and keep modules focused on one command or concern. Follow existing style: 4-space indentation, `from __future__ import annotations` in modules that already use it, snake_case functions and variables, PascalCase classes, and `test_*` test functions. Prefer small command handlers that delegate shared behavior to reusable core functions. Keep user-facing CLI text compatible with the existing Chinese/English i18n pattern in `src/asc/i18n.py`.
+
+## Testing Guidelines
+
+Tests use `pytest` and mocks for App Store Connect interactions by default. Add or update tests in `tests/` for any behavior change, especially command dispatch, config precedence, API retries, guard behavior, and upload validation. Use `tmp_path`, fixtures, and `unittest.mock` rather than real credentials or network calls. Live ASC tests must remain opt-in, for example via `ASC_TEST_LIVE=1`.
+
+## Commit & Pull Request Guidelines
+
+Recent commits use concise Conventional Commit-style messages, such as `feat(update): add --version and --branch options`, `fix(update): skip editable check...`, `test: add tests...`, and `docs: add...`. Follow that pattern.
+
+Pull requests should include a clear summary, linked issue when applicable, test results (`pytest` output is sufficient), and screenshots or sample CLI output for user-visible command changes. Note any credential, App Store state, or CI implications.
+
+## Security & Configuration Tips
+
+Never commit real `.p8` keys, `.env` files, local profiles, or generated credentials. Local project config belongs in `.asc/config.toml`; reusable profiles and keys are stored under `~/.config/asc/`. Use dry-run commands before uploads that modify metadata, screenshots, IAP, or release state.