Skip to main content الرئيسية المنشئون whamp whamp-claude-tools pocketbase-api-add-field
pocketbase-api-add-field This skill should be used when the user asks to "add fields to PocketBase collection", "modify PocketBase schema", "add new collection fields", "update PocketBase collection", "PocketBase JavaScript SDK API", "programmatically add PocketBase fields", or mentions modifying PocketBase collection schemas via API. Provides comprehensive guidance for adding fields to existing PocketBase collections using the JavaScript SDK API.
الانتقال إلى التثبيت سوق المهارات اكتشف واستكشف مهارات الذكاء الاصطناعي التي بناها المجتمع.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
عرض تفاصيل Prompt يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Whamp/whamp-claude-tools --skill pocketbase-api-add-fieldيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
تحميل Zip جاري التحميل... المهن ذات الصلة SOC
استنادا إلى تصنيف SOC المهني
name pocketbase-api-add-field description This skill should be used when the user asks to "add fields to PocketBase collection", "modify PocketBase schema", "add new collection fields", "update PocketBase collection", "PocketBase JavaScript SDK API", "programmatically add PocketBase fields", or mentions modifying PocketBase collection schemas via API. Provides comprehensive guidance for adding fields to existing PocketBase collections using the JavaScript SDK API. version 0.1.0
PocketBase API Add Field
This skill provides comprehensive guidance for programmatically adding fields to existing PocketBase collections using the JavaScript SDK API. It enables developers to modify collection schemas without using the Admin UI, making it ideal for automated migrations, deployment scripts, and programmatic database schema updates.
When to Use This Skill
Use this skill when you need to:
Add new fields to existing PocketBase collections programmatically
Create automated schema migration scripts
Update collection schemas without using the Admin UI
Implement field additions in deployment pipelines
Perform bulk schema modifications across multiple collections
Integrate schema changes into custom applications or tools
Prerequisites
Install PocketBase JavaScript SDK
Install the PocketBase SDK if not already available:
npm install pocketbase
Initialize PocketBase Client
import PocketBase from 'pocketbase' ;
const
new
PocketBase
'http://127.0.0.1:8090'
Admin Authentication Schema modifications require admin privileges. Authenticate using one of these methods:
await pb.admins .authWithPassword ('admin@example.com' , 'your-admin-password' );
pb.authStore .save ('your-admin-token' );
Core Workflow
Step 1: Get Current Collection Schema Retrieve the existing collection to understand current schema:
async function getCollectionSchema (collectionNameOrId ) {
const collection = await pb.collections .getOne (collectionNameOrId);
return collection;
}
Step 2: Define New Fields Create field definitions following PocketBase field schema format:
const newFields = [
{
name : 'bio' ,
type : 'text' ,
required : false ,
options : {
max : 1000
}
},
{
name : 'avatar' ,
type : 'file' ,
required : false ,
options : {
maxSelect : 1 ,
maxSize : 5242880 ,
mimeTypes : ['image/jpeg' , 'image/png' , 'image/webp' ]
}
}
];
Step 3: Add Fields to Schema Merge new fields with existing schema and update collection:
async function addFieldsToCollection (collectionId, newFields ) {
const collection = await pb.collections .getOne (collectionId);
const updatedSchema = [...collection.schema , ...newFields];
const updatedCollection = await pb.collections .update (collectionId, {
name : collection.name ,
schema : updatedSchema
});
return updatedCollection;
}
Step 4: Verify Changes Confirm the schema was updated successfully:
async function verifySchemaChanges (collectionId, expectedFields ) {
const collection = await pb.collections .getOne (collectionId);
const fieldNames = collection.schema .map (field =>name );
return expectedFields.every (field =>includes (field));
}
Complete Implementation Example import PocketBase from 'pocketbase' ;
async function addFieldsToUsersCollection (const pb = new PocketBase ('http://127.0.0.1:8090' );
try {
await pb.admins .authWithPassword ('admin@example.com' , 'your-admin-password' );
const usersCollection = await pb.collections .getOne ('users' );
const newFields = [
{
name : 'bio' ,
type : 'text' ,
required : false ,
options : {
max : 1000
}
},
{
name : 'is_active' ,
type : 'bool' ,
required : false ,
default : true
},
{
name : 'date_of_birth' ,
type : 'date' ,
required : false
}
];
const updatedSchema = [...usersCollection.schema , ...newFields];
const updatedCollection = await pb.collections .update (usersCollection.id , {
name : usersCollection.name ,
schema : updatedSchema
});
console .log ('Fields added successfully!' );
return updatedCollection;
} catch (error) {
console .error ('Error adding fields:' , error);
throw error;
} finally {
pb.authStore .clear ();
}
}
Field Type Examples Common field configurations for different data types:
Text Fields {
name : 'full_name' ,
type : 'text' ,
required : true ,
options : {
min : 1 ,
max : 100
}
}
Email Fields {
name : 'secondary_email' ,
type : 'email' ,
required : false
}
Number Fields {
name : 'age' ,
type : 'number' ,
required : false ,
options : {
min : 0 ,
max : 150
}
}
Select Fields {
name : 'status' ,
type : 'select' ,
required : true ,
options : {
values : ['active' , 'inactive' , 'pending' ]
}
}
Relation Fields {
name : 'team' ,
type : 'relation' ,
required : false ,
options : {
collectionId : 'teams_collection_id' ,
maxSelect : 1
}
}
Error Handling & Best Practices
Validate Field Names Check for conflicts with existing fields:
function validateFieldNames (newFields, existingSchema ) {
const existingNames = existingSchema.map (field =>name );
const conflicts = newFields.filter (field =>includes (field.name ));
if (conflicts.length > 0 ) {
throw new Error (`Field name conflicts: ${conflicts.map(f => f.name).join(', ' )} ` );
}
}
Safe Field Addition Backup and restore schema on failure:
async function safeFieldAddition (collectionId, newFields ) {
const originalCollection = await pb.collections .getOne (collectionId);
try {
await pb.admins .authWithPassword ('admin@example.com' , 'password' );
validateFieldNames (newFields, originalCollection.schema );
const updatedSchema = [...originalCollection.schema , ...newFields];
await pb.collections .update (collectionId, {
name : originalCollection.name ,
schema : updatedSchema
});
} catch (error) {
await pb.collections .update (collectionId, {
name : originalCollection.name ,
schema : originalCollection.schema
});
throw error;
}
}
Authentication Cleanup Always clean up authentication state:
try {
} catch (error) {
console .error ('Schema modification failed:' , error);
throw error;
} finally {
pb.authStore .clear ();
}
Additional Resources
Reference Files
references/field-types.mdreferences/advanced-patterns.mdreferences/error-handling.md
Examples
examples/basic-field-addition.jsexamples/batch-schema-update.jsexamples/migration-script.js
Scripts
scripts/validate-schema.jsscripts/backup-restore.jsscripts/field-conflict-check.js
Key Points
Admin Authentication Required - Collection schema changes require admin privilegesGet Current Schema First - Never assume the current state of the collectionValidate Field Names - Ensure no conflicts with existing fieldsHandle Errors Gracefully - Consider rolling back changes if something failsClean Up Authentication - Clear auth state when doneTest Thoroughly - Verify the schema changes work as expected before production use This approach provides complete programmatic control over PocketBase collection schemas, enabling automated migrations and deployment workflows.
