@anytio/pspm 0.0.3 → 0.0.4

package/README.md

@@ -69,43 +69,58 @@ pspm publish --bump patch     # Auto-bump version (major, minor, patch)
 pspm unpublish <spec> --force # Remove a published skill version
 ```
 
+**Publish Output:**
+
+When publishing, PSPM displays detailed package information similar to npm:
+
+```
+pspm notice
+pspm notice 📦  my-skill@1.0.0
+pspm notice Tarball Contents
+pspm notice   5.1kB SKILL.md
+pspm notice   1.5kB package.json
+pspm notice Tarball Details
+pspm notice name:          my-skill
+pspm notice version:       1.0.0
+pspm notice filename:      my-skill-1.0.0.tgz
+pspm notice package size:  2.3kB
+pspm notice unpacked size: 6.6kB
+pspm notice shasum:        4bb744fcfa90b8b033feed3deaeeb00f3a4503e5
+pspm notice integrity:     sha512-DqQJaugblfE5A...
+pspm notice total files:   2
+pspm notice
+pspm notice Publishing to https://pspm.dev with tag latest
++ @user/username/my-skill@1.0.0
+Checksum: abc123...
+```
+
 ### Configuration
 
 ```bash
-pspm config list              # List all profiles
 pspm config show              # Show resolved configuration
-pspm config add <name>        # Create a new profile
-pspm config use <name>        # Set the default profile
-pspm config set <profile> <key> <value>  # Set a profile field
-pspm config delete <name>     # Delete a profile
 pspm config init              # Create .pspmrc in current directory
 ```
 
 ## Configuration
 
-### User Config (`~/.pspm/config.json`)
+PSPM uses a simple npm-like INI configuration format.
 
-```json
-{
-  "version": 2,
-  "defaultProfile": "default",
-  "profiles": {
-    "default": {
-      "registryUrl": "https://pspm.dev/api/skills",
-      "apiKey": "sk_...",
-      "username": "myuser"
-    }
-  }
-}
+### User Config (`~/.pspmrc`)
+
+```ini
+; PSPM Configuration
+registry = https://pspm.dev
+authToken = sk_...
+username = myuser
 ```
 
 ### Project Config (`.pspmrc`)
 
-```json
-{
-  "profile": "production",
-  "registryUrl": "https://custom-registry.example.com/api/skills"
-}
+Project-specific configuration (optional):
+
+```ini
+; Project-specific PSPM configuration
+registry = https://custom-registry.example.com
 ```
 
 ### Lockfile (`skill-lock.json`)
@@ -113,7 +128,7 @@ pspm config init              # Create .pspmrc in current directory
 ```json
 {
   "lockfileVersion": 1,
-  "registryUrl": "https://pspm.dev/api/skills",
+  "registryUrl": "https://pspm.dev",
   "skills": {
     "@user/username/skillname": {
       "version": "1.0.0",
@@ -124,15 +139,46 @@ pspm config init              # Create .pspmrc in current directory
 }
 ```
 
+### Configuration Resolution
+
+Configuration is resolved in priority order:
+
+1. **Environment Variables** (`PSPM_REGISTRY_URL`, `PSPM_API_KEY`) - Highest
+2. **Project Config** (`.pspmrc` in project directory)
+3. **User Config** (`~/.pspmrc`)
+4. **Defaults** - Lowest
+
 ## Environment Variables
 
 | Variable | Description |
 |----------|-------------|
-| `PSPM_PROFILE` | Select active profile |
 | `PSPM_REGISTRY_URL` | Override registry URL |
 | `PSPM_API_KEY` | Override API key |
 | `PSPM_DEBUG` | Enable debug logging |
 
+## Error Handling
+
+PSPM provides clear, actionable error messages:
+
+**Version Conflict:**
+```
+pspm error code E403
+pspm error 403 403 Forbidden - You cannot publish over the previously published versions: 1.0.0.
+Error: [BAD_REQUEST] Version 1.0.0 must be greater than existing version 1.0.0
+```
+
+**Validation Errors:**
+```
+Error: Validation failed:
+  - name: Skill name must start with a letter and contain only lowercase letters, numbers, and hyphens
+  - version: Invalid semver version
+```
+
+**Authentication Errors:**
+```
+Error: Not logged in. Run 'pspm login --api-key <key>' first, or set PSPM_API_KEY env var.
+```
+
 ## Directory Structure
 
 ```
@@ -145,8 +191,8 @@ project/
             ├── SKILL.md
             └── ...
 
-~/.pspm/
-└── config.json          # User config
+~/
+└── .pspmrc              # User config
 ```
 
 ## Creating a Skill
@@ -195,19 +241,23 @@ export PSPM_REGISTRY_URL=https://registry.example.com/api/skills
 pspm install --frozen-lockfile
 ```
 
-## Multi-Registry Setup
+## Using Different Registries
+
+Use environment variables to switch between registries:
 
 ```bash
-# Create profiles for different registries
-pspm config add production --registry-url https://prod.example.com/api/skills
-pspm config add staging --registry-url https://staging.example.com/api/skills
+# Development
+PSPM_REGISTRY_URL=https://staging.example.com pspm add @user/bsheng/skill
+
+# Production
+PSPM_REGISTRY_URL=https://prod.example.com pspm publish
+```
 
-# Login to each
-pspm login --api-key sk_prod_xxx --profile production
-pspm login --api-key sk_staging_xxx --profile staging
+Or set the registry in your project's `.pspmrc`:
 
-# Use specific profile for operations
-pspm add @user/bsheng/skill --profile production
+```ini
+; .pspmrc
+registry = https://custom-registry.example.com
 ```
 
 ## License